You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "next page" links on the bottom of the homepage don't work. While the link does take you to a new page (as witnessed by the url), the content of the page is still the same top 25 reclinks of the homepage. I've tested this with multiple themes. I'm guessing, the plugin doesn't ever show past the top 25 submissions.
Is this easily fixed? Working "next page" and "previous page" links on the homepage for reclinks?
The text was updated successfully, but these errors were encountered:
Interesting issue. What is your setup? I'm guessing your WP setup is set to use a static page as your home page, and then in the reclinks plugin, that static page is set to hold the recommended links archive? What is your site permalink structure, and what are the urls that the plugins generates to try and reach the second page? Just want to know so I can try and duplicate the problem.
The pagination function works fine in all my tests on the post type archive, or on a static page that's not the home page. If its not working on the home page, it should be an easy fix.
Yes, I'm using a static page as my homepage and then from the plugin settings selected that page for my reclinks archive. I've set my permalinks to "%postname%". The url generated for the 2nd page in the pagination is "http://www.example.com/page/2/".
I've tried with other permalink settings and get the same results.
The "next page" links on the bottom of the homepage don't work. While the link does take you to a new page (as witnessed by the url), the content of the page is still the same top 25 reclinks of the homepage. I've tested this with multiple themes. I'm guessing, the plugin doesn't ever show past the top 25 submissions.
Is this easily fixed? Working "next page" and "previous page" links on the homepage for reclinks?
The text was updated successfully, but these errors were encountered: