# Split topic posts appearing as not having been visited
**URL:** https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070
**Category:** Bug
**Tags:** pr-welcome
**Created:** [March 14, 2017, 10:46am UTC](https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070 "2017-03-14T10:46:36Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@SlyRemarks](https://meta.discourse.org/u/SlyRemarks)
#### Post date: [March 14, 2017, 10:46am UTC](https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070/1 "2017-03-14T10:46:36Z")
A very minor issue we have noticed on our self-hosted Discourse (v1.8.0.beta5 +33) - the issue described in the following topic is still occurring for us (posts that have been split are appearing as not having being visited):
> [@"USER split this topic" makes topic forever "un-visited"](https://meta.discourse.org/t/user-split-this-topic-makes-topic-forever-un-visited/36558):
>
> This topic got off-topic, so I split the the posts to a new topic. Here you can see the new topic is greyed out with class="title visited" because I’ve read it all. The parent topic is still black, with class="title" Doesn’t matter how many times I go into the parent topic to read it, it remains black in the Latest view. This is the case with any topic that’s had posts forked to a new topic. Here’s an old one: However, if I delete the “user split this topic” post…
It doesn’t always behave this way. A topic that I split would not appear “grayed” out to me (an Admin), but it did to another Admin. Moderators have reported the same thing.
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [March 14, 2017, 12:12pm UTC](https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070/2 "2017-03-14T12:12:10Z")
We see the same issue on our forum (running latest).
It only seems to happen if the **last** post on a topic is deleted/split/moved. A workaround is to just make another post on the topic, but that’s left us with a lot of posts that look something like
> [@](#):
>
> making a random post to mark topic read
which is clearly not ideal.
---
### Author:  [@Remah](https://meta.discourse.org/u/Remah)
#### Post date: [April 9, 2017, 11:18pm UTC](https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070/3 "2017-04-09T23:18:38Z")
Have the same problem. It has minor impact but it is perpetually annoying on every Latest view.
The problem arose [when I split a topic](https://forum.glasswire.com/t/glasswire-menu-settings/4322?u=remah) as also reported in:
> [@Split topics don't get "read" styling in list](https://meta.discourse.org/t/split-topics-dont-get-read-styling-in-list/60515):
>
> I believe this is related to: The topic doesn’t show up in my “unread” list, but it doesn’t get the “read” styling in the list – that is, its title is still displayed in black, rather than the expected light grey. It’s not a major issue, but it does make the inbox-zero perfectionist in me twitch. wink
However, I didn’t have this problem when [I split a topic week earlier](https://forum.glasswire.com/t/how-to-download-and-run-the-latest-version-of-the-glasswire-installer/4138?u=remah).
This was apparently fixed so it might be a regression:
> [@"USER split this topic" makes topic forever "un-visited"](https://meta.discourse.org/t/user-split-this-topic-makes-topic-forever-un-visited/36558/3):
>
> This is now [fixed in latest](https://meta.discourse.org/t/long-term-whisper-posts-on-topics/45057/10) courtesy of @sam
---
### Author:  [@Remah](https://meta.discourse.org/u/Remah)
#### Post date: [April 11, 2017, 12:39am UTC](https://meta.discourse.org/t/split-topic-posts-appearing-as-not-having-been-visited/59070/4 "2017-04-11T00:39:15Z")
The only difference that I can think of between the two split topics - apart from the different dates - is that the working split topic had only one post selected whereas the topic with this bug had two posts selected to create the new topic.