Bug tracker

This ticket has been moved to our new tracker. Open Ticket PHPBB3-8416 now.

View unread posts (fix completed in vcs)

This is a post I made in the Discussion of the blog post about 3.0.6 plans and I was encouraged to report it here
OK, phpbb2 had a real issue with unreads - you logout you loose all unreads. With phpbb3 this issue is resolved (unreads can be kept in the db regardless the fact you logged out or not) But since you implemented functions like "View unanswered" "View new posts", "View active topics" why haven't you implemented a "View unread", also?
If a board has 500-600 replies/day this feature is priceless. You click on view unreads, read what you are interested in, click mark read for the rest and voila, all fine...
You login, you read until half of one page, you click "mark as unread" for the first post you did not have time to read and the next time you click to view your unreads, from that post and on they appear as unread. I really never understood the purpose of "View new posts", anyway. If a post was made before your last login and you didn't have time to read it then it is not listed there sometimes, and to find all unreads you must go from forum to forum and click on all the topics that have unread posts.
I was using keep unread in phpbb2 and if asinshesq hadn't created View or mark unread posts I honestly couldn't be able to upgrade to phpbb3 (my members would eat me -alive ... :lol: )
So, how come?

P.S. Many people probably cannot understand the need for this, but I seriously say that once you have this feature and get used to it, then you cannot imagine living without it (really...)
Anyways, since unreads are now marked and never get lost, I hope that this addition will make it to the core of phpbb3. Have a nice day and apologies for the big post... :oops:
PS: I attach a screenshot with the results after clicking "View unread posts" and the arrow drwan there points to the feature to mark all your unreads as read..
Untitled-1.jpg (94.65 KB)

Comments / History

Posted by onehundredandtwo on Jun 16th 2009, 07:53

This is probably one of the first features mentioned by a non-team member that I would actually agree with.

I never really took notice until now, but having a search for unread posts would be soo much more easier than manually looking through to find unread posts.

Assigned ticket to user "bantu"

Action performed by Acyd Burn (Consultant) on Jun 19th 2009, 17:22

Assigned ticket to group "Junior Developers"

Action performed by bantu (3.0 Release Manager) on Jun 21st 2009, 00:27

Assigned ticket to user "rxu"

Action performed by rxu (Former Team Member) on Jun 21st 2009, 14:23

Changed ticket status from "New" to "Fix in progress"

Action performed by rxu (Former Team Member) on Jun 21st 2009, 14:23

Linked ticket with changeset: r9653

Action performed by rxu (Former Team Member) on Jun 22nd 2009, 14:36

Changed ticket status from "Fix in progress" to "Fix completed in SVN"

Action performed by rxu (Former Team Member) on Jun 22nd 2009, 14:36

Posted by ChriZathens on Jun 23rd 2009, 09:41

Great to see that you implemented this, guys...
For the future, please also implement the option to mark a post as unread, otherwise this is not completed.... :(

Posted by ChriZathens on Jun 23rd 2009, 10:02

(Sorry for double-post but there is no other way..)
One major need is the existence of mark all read in the search results...

Importance for the features:
View unreads : 70%
Mark post unread: 20%
Mark all results read :10%

Please implement the rest 30% :oops:

Posted by rxu (Former Team Member) on Jun 23rd 2009, 11:43

The ticket title is "View unread posts", so this is implemented.
There's an option to mark all the forums read on index page.
And I doubt that the feature to mark one particular post read will be ever implemented (imho). You can do it by reading the post actually ;)

Posted by asinshesq (QA Team) on Jun 23rd 2009, 12:11

rxu, your last sentence is a misreading of what chrizathens was saying. THe feature he was talking about was the ability to read a post (or pm) and then mark it as UNREAD (not read). The users on my board find that feature essential - they like to see what a post is and then come back later to finish it or to reply to it.

And by the way, the view unread mod does a number of other things, including correcting a number of phpbb3 bugs in the unread system, that it would be nice if the core code took over. Some of that I list in the author's notes (which is a separate txt file in a readme folder under the contrib folder).

Posted by rxu (Former Team Member) on Jun 23rd 2009, 13:03

rxu, your last sentence is a misreading of what chrizathens was saying. THe feature he was talking about was the ability to read a post (or pm) and then mark it as UNREAD (not read).

Ah... yes, sure. But I think this is completely different feature from "View unread posts" anyway ;)

Posted by ChriZathens on Jun 23rd 2009, 18:35

Well do you mean that we need to issue a different ticket? :)
Although this would be kinda weird, since version 3.0.6 which will include this feature is not released yet...:)
The actual way would be to wait for the release of 3.0.6, then report this missing feature, then -maybe- you'll implement this and it will be released in 3.0.7 (maybe a year from now..)
Anyways, the logic is that you have a button to collect all the unreads, in viewtopic you have the ability to mark a post as unread (this could be considered as a bug, since when you access a page with unreads, the whole page is considered unread... So if you had time to read only the first post, then you loose track of all other unreads in the page.. ;) )
The ability to mark all read from the search results page is also usefull : You read posts you want, mark the rest -which you don't want to read- as read with one click - done!
It is not that difficult to implement afterwards, as a mini-mod, but it would be kinda cool for this addition to be ...feature complete and standard with the core!)
Anyways, I don't mean to get you dizzy, it is just that I strongly believe that this whole feature is a really must have in boards.
No matter what you'll decide to do, I awe you a big thanks for your efforts so far... ;)
Cheers,
Chris

Posted by ToonArmy (Former Team Member) on Jun 24th 2009, 09:21

One ticket, one issue. Just because its in SVN doesn't stop you opening a ticket. ;)

Ticket details

Related SVN changesets