07-08-2017 16:57 - edited 07-08-2017 16:59
07-08-2017 16:57 - edited 07-08-2017 16:59
More and more I'm seeing threads marked as new when they are several days old and I know that I have already read them.
I presume that somebody has decided that some threads are located in the wrong section of the Community.
Surely if threads are being moved to different sections it shouldn't trigger a new thread indicator ?
For example :
https://community.o2.co.uk/t5/Pay-Monthly-and-Pay-Go/Returned-upgraded-phone/m-p/1064321
on 07-08-2017 18:17
on 07-08-2017 18:17
@MI5 wrote:No one is suggesting you shouldn't move posts.
What would be nice is if they didn't appear as unread though once they had been moved.
Alternatively, rename the Home section so people don't get drawn there to post everything?
I agree with all of this and yes @MercedesS please log with Lithium.....although I believe it has been logged previously.
Lithium does seem to be capable of creating it's own unique problems compared to other forum software.
on 07-08-2017 18:57
on 07-08-2017 18:57
I would also point out that O2/Lithium have also failed to correct the problem of new 'unread' posts.
This is where we are taken to the last post instead of the first unread post
This was first pointed out way back in February in More Forum Issues HERE
It still is an issue and time consuming that we have to keep scrolling back in a thread to find the last post we read. Toby was the first to look at it as a problem....then @Martin-O2 checked again in March. We were given the response that it had been reported and Lithium were looking at a fix.....??
Veritas Numquam Perit
on 07-08-2017 19:04
on 07-08-2017 19:04
It just seems impossible to get things repaired or ideas implemented....
on 08-08-2017 09:20
on 08-08-2017 09:20
@Cleoriff wrote:
I would also point out that O2/Lithium have also failed to correct the problem of new 'unread' posts.
This is where we are taken to the last post instead of the first unread post
This was first pointed out way back in February in More Forum Issues HERE
It still is an issue and time consuming that we have to keep scrolling back in a thread to find the last post we read. Toby was the first to look at it as a problem....then @Martin-O2 checked again in March. We were given the response that it had been reported and Lithium were looking at a fix.....??
Hello @Cleoriff,
If it is not working, this one is our fault for sure. As @Martin-O2 said, it should be fixed by Lithium long ago. We tested on our computers and phones and worked just fine. So my bad because I thought it was working for everyone when it was working for us. I am really sorry.
Can you please help us understand why it doesn't work for you?
What we have tested:
1. Go to Unread Posts on the top [link here]
2. Then you can see the list of last messages [where you can decide to see Discussions or Post]
3. Then click on the ones with the Unread mark and... it goes to the last one.
Please please, if it is not working let us know so we can try to talk to lithium to fix it. And I am sorry for this one.
on 08-08-2017 09:54
on 08-08-2017 09:54
on 08-08-2017 09:56
on 08-08-2017 09:56
@MI5 wrote:
It used to go to the individuals last read post, not the last post in the thread.
So... it doesn't work for you @MI5? Does it go to the last post in the thread and not to the last one for you?
on 08-08-2017 10:01
on 08-08-2017 10:01
on 08-08-2017 10:05
on 08-08-2017 10:05
@MI5 wrote:
Correct, not working for me as I would like it.
If you can help me with more information I will open again a case to Lithium!
on 08-08-2017 10:11
on 08-08-2017 10:11
on 08-08-2017 10:24
on 08-08-2017 10:24
@MI5 wrote:
I always access forum from "unread posts "
If there are a number of replies on a thread, the reply you click on goes to that post so I have to go the the very last post in the list for that thread to get to the last one I read.
This happens on windows 10, 7, chrome and safari.
Exactly the same for me @MercedesS I use my PC mainly (either Firefox or Chrome).. but I still get the problem if I use my mobile (using Chrome)
It affected everyone who posted on the thread 'More Forum Issues'. (I gave the link to where it was first mentioned way back in February 2017) Toby and then Martin said it was a bug and O2 were looking for a fix...
Veritas Numquam Perit