Found out: I'm usually developing with XAMPP (A WAMP-installation package) on my local computer before uploading pages to the customers servers.
Your static method c_ws_plugin__s2member_systematics::is_systematic_use_page () has a rule (line 40) wich returns true on local hosted pages requested by the local browser. That intentionally prevents the execution of the security code from line 63 in pages.inc.php.
Is there a reason you unlock every page on a local dev-system? Could that be moved into an configurable option?
Btw. What stands against a deeper integration into the wp-pages/post/category interface to secure these instead of manually entering IDs into the s2member general options page?
There are easy ways to insert functionality into the wp quickedit pane and the normal edit/create post page (i've done that for several plugins). That way the users would not have to hazzle with IDs (and remembering them I could send you some code samples if you're interested: I do have made a little plugin with postpage quickedit integration some days ago.
just my 5 cents,
greets from Salzburg!
- JohannesStatistics: Posted by jjarolim — April 18th, 2011, 1:28 am
]]>