Page 1 of 1

Restricting non-WP pages

PostPosted: July 24th, 2011, 9:13 am
by myassis
Hi.

Is there a way on restricting access to other pages,non wordpress site on other server/domain. Perhaps by including some code in the pages to restrict access. Whereby this code will verify the access with the s2Member plugin on different server.

tq

Re: Restricting non-WP pages

PostPosted: July 24th, 2011, 11:45 am
by glbrent
From the information give. You have two general options here that I see. Assuming you are an administrator of the other site, you could do a double login through the API > scripting or API > notification through scripting. Second, would be to recreate all those pages on your website through perhaps an Iframe in HTML on each one of your pages. Then you can lock down the Iframe pages locally through page restrictions.

Re: Restricting non-WP pages

PostPosted: July 24th, 2011, 3:04 pm
by myassis
After read through all those links,and explanation....I still didnt find any reference to get it work on non-WP site on different server/domain.....maybe I missed something... :?:

Re: Restricting non-WP pages

PostPosted: July 25th, 2011, 12:25 am
by glbrent
Depending on what you have on this second server, forums, secure content, etc. You are probably looking at a custom code job. That second server has to be setup to talk to S2member. I am doing a deal like that as well, and it works really slick but that server must be running a script waiting for authentication, checksums and input from s2member. You must consider what variables you are going to send. Then it's a matter of programming. This process can get very tricky. So it all depends on what level you want to take it to. If you stick with s2member you at least have 1/2 of the equation plus payment gateway done for the programmer. That's my 2 cents; Best of luck! :)