LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
The marking will always use the last time you clicked "Mark All Read". Your session timing out no longer has any impact on thread or forum read marking in any way.
Where do I find "Mark All Read" I looked in thread tools and possibly at the bottom in a drop down box but I still can't find it. Any hints would be appreciated.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
Additionally, since the link is more important now; I'd be willing to add it to the MyLQ side nav if there is member interest (and if we decide to keep this method of Read Marking over the old session based one).
Additionally, since the link is more important now; I'd be willing to add it to the MyLQ side nav if there is member interest (and if we decide to keep this method of Read Marking over the old session based one).
--jeremy
That would be nice, because it has become more necessary to click it, and it takes some clicking to find.
If you click "View Latest Threads" immediately after clicking "Mark Forums Read" you should see "Sorry, there are no new threads to view." This very reproducibly happens for me. Anything else would be a bug (unless you see one or two threads, which means someone actually did post between clicks).
It is very, very different for me. When I click on "View Latest Threads" right now, I get a list with header "1451 New Posts (from the last 7 days)" followed by all the threads with activity in the last 7 days (30 pages worth). In the old system, the threads with activity since my last visit would be in bold. Now, the only threads not in bold are those threads I have actually read since their last activity.
I tried selecting "Month" as the "new post" period, and of the "4811 New Posts" displayed, all threads older than 14 days are considered "read". All other threads that I have not actually read are considered "new" and displayed in bold.
I'm running an RHEL 6 clone with Firefox 3.6.24. I've tried clearing cache and disabling NoScript, with no effect on this. All sites are allowed to store session cookies, and linuxquestions.org is allowed to store persistent cookies.
Wait a minute. Aren't you describing the "View New Posts" link and not "View Latest Threads"?
Last edited by rknichols; 11-29-2011 at 08:41 AM.
Reason: Add "wait a minute"
At last I understand (hopefully). Instead of the system telling me which posts have been made since I was last here, I have to remember to tell the system what to mark before I go. What I don't understand is why that is an improvement.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
Quote:
Originally Posted by rknichols
It is very, very different for me. When I click on "View Latest Threads" right now, I get a list with header "1451 New Posts (from the last 7 days)" followed by all the threads with activity in the last 7 days (30 pages worth). In the old system, the threads with activity since my last visit would be in bold. Now, the only threads not in bold are those threads I have actually read since their last activity.
That's the expected behavior, if you don't click "Mark Forums Read".
Quote:
Originally Posted by rknichols
Wait a minute. Aren't you describing the "View New Posts" link and not "View Latest Threads"?
I was indeed, thanks - my post has been corrected.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
Quote:
Originally Posted by DavidMcCann
At last I understand (hopefully). Instead of the system telling me which posts have been made since I was last here, I have to remember to tell the system what to mark before I go. What I don't understand is why that is an improvement.
It's possible that the new system is not a perceived improvement, which is why we're soliciting feedback. Keep in mind that the system was never intended to identify which posts were made since you were last visit, but which threads you have read. Without a persistent way to keep track of which thread you actually read though, your session timing out simply marked all threads "read" based on the post time (which is really not an ideal solution). Out of curiosity, what do you not like about the new system?
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
Quote:
Originally Posted by rknichols
But I have been clicking on "Mark Forums Read", repeatedly. "Mark Forums Read" has absolutely no effect on the "View Latest Threads" pages.
I apologize for the confusion. The current "View Latest Threads" is a custom time based search that isn't currently aware of the new database-based thread marking system. We'll look into getting it updated.
I do not want "View Latest Threads" to be aware of the new database-based thread marking system. I use the "Mark all threads read" to remove zero reply entries from my CP which I am subscribed to. That is the only way to stop them from showing up in my adminCP until someone replies to them.
So I wouldn't be able to view the latest threads if I press that to get rid of the zero reply threads in my saved subscriptions. I would be cross.
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,604
Original Poster
Rep:
sag47, "View Latest Threads" being aware of the new system wouldn't cause the threads not to show up (since that is by design a time based search), it would cause the threads before the last time you clicked "Mark all threads read" to not be bolded.
Ah I see. Well then that would be okay. Also rather than me having to click the scary nuclear bomb of mark all threads read it would be nice to have a thread tool to mark a single thread read since I'm working in the scope of a few zero reply threads at a time it wouldn't be a problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.