After that amount of timeout, currently 10 days on xf.com, posts are marked as read - even of they have not been read.May I ask what 10 day timeout you are talking about?
It also means that once posts are marked as Read, a user opening a New Thread (to that user) gets bumped to a post near the middle or end of the thread.After that amount of timeout, currently 10 days on xf.com, posts are marked as read - even of they have not been read.
You already can do that from what Mike and Kier have said.It also means that once posts are marked as Read, a user opening a New Thread (to that user) gets bumped to a post near the middle or end of the thread.
This is confusing as it's not intuitive to open a new thread and it doesn't open at the first post. It's OK if it's obviously an old post like 6 months ago maybe but otherwise it's very confusing.
So yes it's important that we c an set the timeout as a lengthy time period.
On a very busy board with a high turnover of content, setting a high limit could result in very large quantities of data and a possible performance penalty - however on these kind of boards there tends to be less thread necromancy, so the problem is mitigated and a smaller timeout is less of an issue.
On a small to medium board that has plenty of disk space and doesn't tax its server, you could easily set a timeout of a few months without a problem.
Really has no relationship...Post cache and APC will be your friend - or in this case, won't that matter? (talking about 28 days on big-boards)
XenForo practices the black arts... thread necromancy ...
We use essential cookies to make this site work, and optional cookies to enhance your experience.