blog next page generates a 404 error

[kgweber]

I'm having a problem with my site where a link seems to be getting re-directed and generating a 404 error, but only when s2member is enabled.

The problem is easy to reproduce. The site is http://proxyexhange.org. If you go to the home page without logging in, you'll see a bunch of blog posts. Scroll down to the bottom and you'll see links to go to the next page by selecting the Next link. The Next link points to:

http://proxyexchange.org/page/2/

However, when you select that link, the URL changes to

http://proxyexchange.org/2/, which generates a 404 error.

When I disable s2member, the site works fine, displaying the second page of blogs. The problem occurs even when I enter the URL in the browser directly.

Is s2member somehow removing the "page/" from the URL? I don't see any options to configure this.

I have the latest version of s2member installed, but I don't know when this behaviour started happening. I don't think I have any special POST restrictions configured that could explain this behavior.

[Cristián Lávaque]

That's really weird. I see it's a 301 redirection. No, s2Member doesn't have a setting for this. What WordPress and s2Member versions do you have?

Do you have a /page/ directory in your server that may be overlapping with the WP permalink? Did you check your .htaccess file for a redirection rule? If you deactivate other plugins (as a test) leaving s2Member, does the problem continue? If you change the theme (as a test) to TwentyEleven, does the problem continue?

[kgweber]

After looking into this further, it seems to be an interaction with the Canvas theme and the Magazine template. When we configure the site to use a custom Front Page with this template as the home page, this odd behavior occurs. Have there been any other reports of problems with this theme and s2member?

[Cristián Lávaque]

Thanks for the update. I'm glad you found where the problem is.

I don't remember reading other reports of this conflict. You may want to contact the theme's developer so he can look into that and fix it.