Access restrictions not working

[behnt]

I am a bitlazy and did not want to type this one out but page access restrictions are not working for me and I have no idea why here is a screen cap to show you what is happening.

http://screencast.com/t/N2E4YTcwZGUt

Ben

One thing I left out is that I have things set up for the member profile page to go to the login welcome page. Yet it does not redirect like it should it takes one right to the wp-admin page?

[Jason Caldwell]

HI Ben. Thanks for purchasing s2Member Pro.
~ and for the video walk through!

Here are some possible causes that I'm aware of:

1. You've not yet configured a Membership Options Page?
( s2Member will not enforce security restrictions until this has been configured ).

2. Your Membership Options Page is set to the same /content/ page?
( s2Member will NEVER allow the Membership Options Page that you configured to be protected from public access, because this special page must always be available to unregistered Users ).

3. You had a caching plugin installed prior to installing s2Member?
( s2Member is compatible with Quick Cache and WP Super Cache )
However, you may need to reset your cache during the initial testing phase.

4. Another plugin is causing a conflict. I noticed in your video that you're running WooTube and Wassup. I can confirm that s2Member IS compatible with both of those. So no worries there. If you have other plugins installed, you might want to disable them temporarily and re-test until you find the culprit.

If you rule out all of the above, and the problem still exists, please send me an FTP login to your /plugins/s2member/ directory. I'll run some quick diagnostics and explain what's behind the issue. If you send me an FTP login, please use this contact form for security purposes.

[behnt]

1. You've not yet configured a Membership Options Page?
( s2Member will not enforce security restrictions until this has been configured ).

Membership Options page is configured at http://usingsolidworks.com/membership-options-page/

2. Your Membership Options Page is set to the same /content/ page?
( s2Member will NEVER allow the Membership Options Page that you configured to be protected from public access, because this special page must always be available to unregistered Users ).

No it is not the content page is http://usingsolidworks.com/content

3. You had a caching plugin installed prior to installing s2Member?
( s2Member is compatible with Quick Cache and WP Super Cache )
However, you may need to reset your cache during the initial testing phase.

I have not installed any caching plugin but if I did it would have been WP Super Cache

4. Another plugin is causing a conflict. I noticed in your video that you're running WooTube and Wassup. I can confirm that s2Member IS compatible with both of those. So no worries there. If you have other plugins installed, you might want to disable them temporarily and re-test until you find the culprit.

Plugins I use are:
Askimet (Testing showed no change and thank god for that I depend on this one!)
KB Robots.txt (Testing showed no change)
Wassup (you state that this is compatible so I did not test)
Widget Context (Testing showed no change
WP Show IDs (Your plugin mentioned in videos and I assume it works and I did not test)

Soooooo nope it was not the plugins....

If you rule out all of the above, and the problem still exists, please send me an FTP login to your /plugins/s2member/ directory. I'll run some quick diagnostics and explain what's behind the issue. If you send me an FTP login, please use this contact form for security purposes.

Sending in 5 min

[Jason Caldwell]

Hi Ben. Thanks for reporting back on this topic.
I just received your login details and took a quick look.

In your Dashboard, under:
WordPress® Settings -> Reading

Your /content/ Page was configured as your "Posts Page" in WordPress®. So this changes the way WordPress® handles things internally, because it now considers what is actually a Page ( /content/ ), to be an archive, and NOT a Page. In other words, s2Member was unable to determine what /content/ actually was; and therefore security restrictions were not being handled properly.

Possible solution:
If you plan to protect a "Page" with s2Member, be sure you don't assign
it as the "Posts page" in your Reading options for WordPress®. This causes a conflict.

@TODO :: * Note. This marks the first time I've seen this.
I'll see what we can do in a future release to accommodate this scenario.

Please report back if you can. ~ Thanks.

[behnt]

Drat! I was hoping to launch today....
Now I am going to have to rebuild the site. I was hoping to have a funnel page to get signups and not have to put the blog in a sub directory and build a static HTML page to have people land on. Bummer! Anyhow it is what it is. However I set up websites like this on a regular basis and this is a common setup with moving the blog (or posts page) back and putting in a landing page as the root page, so if you can figure it out how to handle this with S2member it would be AWESOME (at least for me )

FWIW all restrictions do not work on that page i.e. If I put in a post restriction it does not handle it properly on that page as well.

Last thing, and I am hoping on a work arond here. Is there a way to have things set up so that I allow access to 2 pages to the general public and the rest blocked, but here is the catch when I use the URI '/' block? I would like to block access to all but the landing page which will be a sub URI such as /Landing-Page and the membership options page but all other pages and content is blocked? Clear as mud?

[BoweFrankema]

edit: I see that you want to allow access to certain pages only.. ok.. hmm.. read it wrong.. I don't know how to achieve what you're asking.. sorry