About: Stephen Carroll

Hello Eduan,
This problem occurs on a new installation with no other plugins. Here are the steps to re-produce the problem:

1) Install WordPress 3.4.1
2) Install s2Member plugin
3) Set WP_DEBUG to true in wp-config.php

Please fix the problem by appending:

cache_needs_updating = false;

to line 45 of cache.inc.php

Also, another warning is thrown “Undefined index” in admin-notices.inc.php.

Please fix the problem by appending:

$_GET["page"] = isset( $_GET["page"] ) ? $_GET["page"] : '';

to line 135 of admin-notices.inc.php.

Again, these problems will not affect most users that do not have WP_DEBUG set to true, as they are just warnings. But this problem will affect users doing website development that have debugging turned on. A properly coded plugin should not throw these warnings as it makes website development difficult and can invoke ‘header already sent’ errors -real errors that inhibit development. Likewise, these warnings indicate are true: variable parameters should be checked and initialized accordingly.

Lastly, I’ve submitted the fix for you above. Please simply incorporate these changes so I don’t have to each time the plugin is updated.

Thank you!

Regarding Custom Capabilities: These are *not* WordPress capabilities.

That’s odd. Because the documentation says “offered by WordPress Roles/Capabilities”. The video also says “…WordPress Roles/Capabilities”.

It also appears to work with “WordPress Capabilities”. But there is a bug:

While s2Member generates a “WordPress Capability”. The problem is that when a user’s WordPress Role is associated with a capability and then that capability is revoked, the capability is not removed. This is because s2Member actually stores the capability in the “user capability textbox” as can be seen in the user profile page. However, it does not properly update the user meta information when his or her role is updated.

My solution, as I stated above, is to manually clear the “capabilities” textbox prior to saving the user’s profile page. To automate this, I simply created a jQuery that clears the textbox whenever a role is changed on a given user.

Please consider reviewing the documentation and video above for “WordPress Capability”.

Again, great product. Thank you!

Never mind! I get it now. The Metabox’s comma delimited capabilities is using AND logic for access. I just assumed it was OR. The later isn’t as efficient anyways as it just makes more sense to assign users a given capability rather then append it to the page. AND logic ensures proper access levels and favors on protecting content -which is nice. Thanks! Works well.

:-)