vBulletin 4 Request - Cookie based post marking....

[woodmj]

Just wondered if there's anyway to add this back to VB4.2.4 through some kind of mod? as it gave different results to the now enforced database marking system.

[Paul M]

First of all, it wasnt removed from 4.2.4, it was removed from 4.2.5.

Secondly, its an ancient system that you should ditch anyway, not sure what you mean by different, but it will give corerct results.

(at the point of switching, you may get unexpected results as no data is transferred from one to the other).

[woodmj]

Sorry to disagree but this happened to my forum upgrading from 4.2.3 to 4.2.4. We are not running the 4.2.5 beta. I am simply passing on member complaint.

[Paul M]

Since I made the change, I think I know which version I removed it from

In 4.2.5 the option has gone.
In 4.2.4 you will be switched to DB marking, but the option isnt removed.

You didnt answer what you mean by "different".

[woodmj]

@ Paul M - Ok, hmm, so, just because something's marked 'deprecated' it doesn't necessarily mean it's gone, just yet :erm: (Note to self)


Basically what we found with Database Marking was when you clicked on New Posts you got the same list you got from Whats New or Recent Activity rather than what used to come from New Posts. With Cookie Marking New Posts only shows any new posts that you haven't read. If there were no new posts it would show "No new posts" or something like that.

[MarkFL]

Originally Posted by woodmj

@ Paul M - Ok, hmm, so, just because something's marked 'deprecated' it doesn't necessarily mean it's gone, just yet :erm: (Note to self)


Basically what we found with Database Marking was when you clicked on New Posts you got the same list you got from Whats New or Recent Activity rather than what used to come from New Posts. With Cookie Marking New Posts only shows any new posts that you haven't read. If there were no new posts it would show "No new posts" or something like that.

In my experience, it is cookie based marking that continues to show threads in the "New Posts" search even after you've read them, and removes them when your cookies expire even if you haven't read them. It is also the cookie based system that chokes, and forces you to clear your cookies to continue, when you perform a large number of tasks on a site.

I recommend to everyone I help that uses the cookie based system to use db marking instead, as I feel it is superior in every way.

[Mark.B]

The whole idea of 'New Posts' is to show posts you haven't read.
If it shows you posts you've already read, it's completely pointless.

If you have members who want that functionality, change the usergroup permissions on Today's Posts instead, so it shows to members. Then they get a list of all posts in the past day (or whatever time period you want basically), unread ones are bold, read ones are non-bold.

[Paul M]

Originally Posted by woodmj

Basically what we found with Database Marking was when you clicked on New Posts you got the same list you got from Whats New or Recent Activity rather than what used to come from New Posts. With Cookie Marking New Posts only shows any new posts that you haven't read. If there were no new posts it would show "No new posts" or something like that.

Correct, when you click on New Posts, you get New (unread) Posts.
(Which is how it should work, if you have read it, its not "new" anymore).

If you want to see both read and unread, use "Todays Posts".

(As well as doing the above correctly, db marking also works across multiple devices, so if you read it on one, it wont show up as unread on another, which cookie marking could never do).

[woodmj]

This is kind of hard to explain but here are screenshots of the different outputs.

We're kind of used to the Cookie one for many years so if we're able to retain that in some way beyond 4.2.4, in whatever way, that would be great. If not I'm sure we'll get used to the other one.