Notifications
Clear all

wpForo 1.x.x Topics loading Page 1 or Post 1 before going to first unread post

2 Posts
2 Users
0 Reactions
109 Views
Posts: 24
Topic starter
(@udpride)
Eminent Member
Joined: 10 months ago

Im running into an issue and may have been dealing with it since installation. On topics that have multiple pages of posts, if you click the topic it should take you to the first unread post. And it eventually does that, but it first appears to load the first page of the topic, and then reloaded again to the last page or whatever page is needed to take you to the first unread post. This "snap" effect of loading Page 1 then the page it takes you to is not forum specific. It seems to do this on all topics with multiple pages.

In Threaded Layout forums, I have my parent posts per page set to 25. I do have "Stick Topic's First Post to Page" for multiple page topics. I dont know if that might be causing it.Ā 

Its very strange. It always seems to initially jump to the first page or original post in the topic, then reload the site to the appropriate page/post it needs to go to based on last unread post.

Example here of a multi-page threaded post:

https://www.udpride.com/forums/mens-basketball/2025-coaching-carousel/

Not sure if you need to be logged in as a user to track last page viewed and stuff to reproduce the issue, but this issue is not user-based because I have noticed it and my users notice it as well.

There's gotta be a reason for it and way to eliminate it.Ā  Any ideas?

1 Reply
Sofy
Posts: 5207
 Sofy
Admin
(@sofy)
Support Team
Joined: 7 years ago

Hi,

This is designed to optimize the wpForo plugin. We have implemented it this way because it significantly improves performance, making the plugin work much faster.

Disabling this function will trigger numerous SQL queries, which can slow down your website.

If you want to override this behavior, you can add the following hook:

add_filter( 'wpforo_build_direct_unread_post_url', '__return_true' );

After adding this code, be sure to clear your cache and check again.

Reply