Not planned Show only unread watched threads rather than all of them

[Naz]

Previously, on XF1, the watched threads page would only show unread watched threads with an accessible link to access a list of all of them.

Unfortunately, on XF2, this is no longer the case and the watched threads list (https://xenforo.com/community/watched/threads) shows all watched threads (regardless of read status) with no way to filter out threads that have been read.

 

[Chris D]

You'd do this from "New posts" now.



You can even save it as your default, if that's how you roll.

 

[Naz]

Neat, never noticed the watched content option there.

 

[Chris D]

With that in mind, I'll call this "Not planned".

It's best to consider the "Watched x" pages as mostly being about management of watched content, now, rather than using it as a new content discovery tool (which is what New posts / What's new is).

 

[RobParker]

We had a few users request the same thing (mainly because it's what they were used to from XF1).

Is it possible to add a navigation link to a specific filter as that would resolve the issue?

i.e. We'd add a "Watched and Unread" link to the nav and link it to posts filtered by unread and watched.

 

[Chris D]

https://xenforo.com/community/whats-new/posts/?watched=1&unread=1

 

[RobParker]

The navigation currently uses stuff like {{ link('watched/threads') }}

Would I just add something like {{ link('posts/?watched=1&unread=1') }} then?

 

[Chris D]

You can just use the full URL if you wish, but to use the XF link builder:

{{ link('watched/posts', null, {'watched': 1, 'unread': 1}) }}

 

[Steffen]

Thank you for the link although IMHO it feels like a workaround.

If the watched posts page is mostly about "management of watched content" now and not a "new content discovery tool" then I think that https://xenforo.com/community/whats-new/posts/?watched=1&unread=1 should get a prominent link in the navigation.

(What I'd actually prefer is an "unread" filter on https://xenforo.com/community/watched/threads as originally suggested because that's also what users migrating from vBulletin are used to.)