Community Support Forums

Hi all,

I have a question regarding to "Specific Post/Page". I made a "page" in wordpress, then in "s2Member->general options->Specific Post/Page Access Restrictions" I wrote the "id" of that page. But still anyone can access to that page.
I test the application in sandbox with PayPal after generated the button, and everthing was ok.. I got the "link" so I can access to that page and download the content (or whatever). the link is something like

http://www.mypage.com/nameOfThePage?s2m ... mRFdzlE.... ,

I notice that the link works, and If I try to modify the key it wont work, but I just type
http://www.mypage.com/nameOfThePage it will work perfect... so, how to block that page and make it accessible only by the token given by s2Member?

thank you!

Are you sure you're not logged in to your admin account when you view the Specific Post/Page? Admins are not subject to s2Member's restrictions.

Also, watch this video http://www.s2member.com/content-restric ... ble-video/

Hi to all! I'm working on this great plugin and I have the same problem reported by cgcamilo.
In Restriction Options -> Specific Post/Page Access Restrictions I put the ID of a post.
Then I created the paypal button and I included it into another page.
Anyway, if I visit the url of the post on sale (as not-member or not-logged) this post is always visible, not hidden...
I already watched the video tutorial but no ideas...
Why? Have I forgot anything?
Many thanks for the help

groucho, make sure you're not logged in when you try to see the protected page, and check that you're not getting a cached copy of the page. Also, make sure you haven't protected the same page with a Level restriction, since this conflicts with the Specific Page restriction.

The same is happening with me. I just began configuration and created the defaults from the tutorial.

Membership Option Page
Login Welcome Page
Protective Page

I set up the general configuration of s2 and still ALL pages are available without being logged into the system.

I'm asking Jason about it.

Many thanks for the reply, Cristián.
Now the page is properly restricted: I think the issue was a cached copy of the page.

groucho75 wrote:Many thanks for the reply, Cristián.
Now the page is properly restricted: I think the issue was a cached copy of the page.

I'm glad that solved your problem.

For others reading this thread, you might find this post helpful also.
viewtopic.php?f=4&t=318&p=16685#p16685