Fork me on GitHub
Subscribe 2

Ticket #924 (open enhancement)

Change the management of unread messages

  • Created: 2013-11-24 10:44:38
  • Reported by: bagu
  • Assigned to: None
  • Milestone: None
  • Component: usability
  • Priority: normal

Management of unread messages is really problematic on FluxBB .

It is basically the only forum system which, when you post a message , makes it appear as "New contribution" , even for the author of the contribution.

In addition, new messages management based only on time makes the reading laborious.

In fact, when I go to a subject containing the new message, I expect it removes itself from new contributions. And this without requiring the user to click "Mark all threads as read".

Similarly , if a user begins to read new posts one day, he/she MUST end quickly if he/she does not want the rest of its unread messages disappear from the list .

In fact, it is currently not possible to leave a message on the side to read a week later for example…

It's very daunting and FluxBB is the only manage new messages this way.

So I can well understand that it may be necessary to define a period of visit’s interruption, but we should be able to adjust for a long time without harming the new messages’ manageent.

Similarly, once a thread has been visited, you should automatically see this thread disappear from the list of new contributions.

Is there therefore a way to do this easily?

A idea would be for example to store the base id subjects visited such as new contributions are automatically excluded ?

The result will then be: List of new topics since last visit MINUS threads already visited by the user EQUAL real new threads

And when you click on "Mark all threads as read" or the period of visit’s interruption is reached, the list of threadds read by the user is emptied.

This will be more flexible and more understandable to the user.

(Refer to ticket 810)


Visman 2013-11-24 11:24:38

It is necessary to transfer tracked topics to a database.
However, the current diagram of database requests doesn't allow to make it without adding new request sad

bagu 2013-11-24 13:03:58

This mod : … -database/

Already transfert tracked topic in database. And it work fine.

Franz 2013-11-24 14:45:19

bagu wrote:

It is basically the only forum system which, when you post a message , makes it appear as "New contribution" , even for the author of the contribution.

Huh? That's not true.

bagu 2013-11-24 14:49:12

Understand, "the only forum system" I USE and I know wink

Franz 2013-11-24 15:10:19

No, the fact is simply not true. If you post a new topic, it will not be marked as unread for you.

Or rather, it will be marked as read immediately as you're redirected back to the topic.

Comment edited 1 times (Diff)

bagu 2013-11-24 15:38:40

Mistraduction i think

I dont mean marked as unread, but it appear "new" when you click on new in the bar :

"Topics: Posted | New | Active | Unanswered"

It appear new, but read.

It wont if we consider i am the author of the post, my own topic may not appear on this list.
1-Because if the topic is new for others, we already know the content of this post.
2-Because we already read the content (because i wrote it)

Comment edited 2 times (Diff, Diff 2)

Visman 2013-11-24 16:07:09

At me sometimes the read topics are marked as new after my short absence at a forum.

bagu 2014-02-16 14:53:24

After a short survey of my users, it appears that the confusion between new messages and messages lately is the problem.
When trying to view new messages, you should see the new and unread messages.
And when we try to see recent posts at this time, we should see the read and unread messages that are recent.

But the two links should work distinct manner.
It would be more logical and easy to use.

In french :
un court sondage auprès de mes utilisateurs, il en ressort que la confusion entre nouveaux messages et messages récents est la cause du problème.
Quand on cherche à voir les nouveaux messages, on ne devrait voir que les messages nouveaux et non lus.
Et quand on cherche à voir les messages récents, à ce moment là, on devrait voir les messages lus et non lus qui sont récents.

Mais les deux liens devraient fonctionner de manière bien distincts.
Ce serait plus logique et plus simple d'usage.

Comment edited 4 times (Diff, Diff 2, Diff 3, Diff 4)