Thanks for reporting this important issue.~and thank you for bringing this to my attention Cristián.So everything in your configuration sounds good. I was surprised to here that reverting to the default WordPress theme and removing all other plugins from the equation has not produced any positive result.
One way to see what is actually going on, is to look in the address bar of your Membership Options page. Whenever s2Member redirects you to the Membership Options Page, it also includes details in the
?query string of the URL about why it forced the redirection. So this would be a good place to start analyzing what is actually causing s2Member to act funny on your installation.
From the documentation ( Membership Options Page Variables ):- Code: Select all
Membership Options Page Variables:
At the core of s2Member, is it's ability to protect content ( i.e. Posts, Pages, Tags, Categories, URI word fragments, etc ). Whenever a public User, or even an existing Member attempts to access an area of your site that is unavailable to them; either because they are not logged-in, not a paying Member at all; or maybe they are logged-in, but they don't have access to content you've protected at a higher Membership Level; — s2Member will always redirect these un-authenticated requests to your Membership Options Page. So your Membership Options Page is a key element of your site. It serves as the focal point of your s2Member installation.
Understanding this, it becomes important for s2Member to provide information about what the User/Member was attempting to access ( before they were redirected to the Membership Options Page ). This is where s2Member's MOP Vars come in ( i.e. Membership Options Page Variables ). Whenever s2Member redirects a User/Member to your Membership Options Page, it will include these important MOP Variables in the query string of the URL. These Variables can be used to provide more informative messages; or even to provide a different set of Membership Options ( i.e. Payment Buttons ), based on what a User/Member was attempting to access.
* Further details available in your Dashboard, under: s2Member -> API Scripting -> Membership Options Page Variables.
So here are some things I would check on.1. After you're redirected to your Membership Options Page, what does the full URL ( including all query string variables ) look like? Does it provide you with any indication as to why you don't have access?
2. Are you really logged in so that s2Member can recognize your Access Level?
Please read this VERY important article that talks about the difference between links with the www. prefix, and without.
viewtopic.php?f=36&t=1066 ( this gets a lot of people )3. Are cookies actually being set in your browser? Is WordPress® recognizing you as a logged-in Member?
Here is one way to test. Pop this Shortcode into a Page:- Code: Select all
[s2Get constant="S2MEMBER_CURRENT_USER_ACCESS_LEVEL" /]
If nothing gives, please email me a
Dashboard login through this form and I'll have a look for you.