VegasKev

Okay…here is what I’ve found…

1.) Giving a role the “read” capability is what gives them access to the wp-admin. However, S2 has that blocked, as the “read” capability is assigned to the lowest role “subscriber”, which S2 Member reserves that role for “trial” and “non-paying” members.

2.) Apparently the “edit_posts” capabilities is the other capability that gives a user access to the wordpress admin when S2Member is installed. The only problem with that is that it gives a user all the access to start playing around with creating posts and sliders (using the flex slider on my theme and slides are created with custom posts).

3.) Unfortunately, even though I can give a quasi-admin the “edit_posts” capability and then just deny any post submissions, the problem now is that when giving the “add_user” and “create_user” capabilities, the quasi-admin has complete access to the S2 Member Menu item in wp-admin and can completely screw up the entire membership platform if they wanted to.

So…..here are the options that I can think of to keep everything as fail safe as possible.

1.) Have S2 Member not dissallow wp-admin with roles using the “read” capability. (though, I fear that would screw up a huge amount of functions within S2 Member)…that being stated, I fear this would not be an option.

2.) Have S2 Member create a capability in the wordpress role manager that would allow access to S2 Member such as “access_S2 Member”. The problem with that is that I fear it would screw up custom roles that existing S2 Member users already have and force them to manually go in and add this new capability to custom roles that they’ve created.

3.) Have S2 Member create a capability that does reverse of what a capability normally does and actually BLOCK S2 Member menu item and functions, such as “block_S2Member_menu”. This way, I can still give someone access to create a user, without giving them access to all of S2 Member functions, thus risking the chances that they will try to play with S2 Member and screw up all of the configurations.

Hopefully we can make some progress with this. I’m sure that people with massive membership sites could use this option as quasi-admins can sometimes become a “MUST HAVE” scenario where the site management is divided between multiple people. Being the head developer, I don’t have time to manually create users on the backend when necessary, yet for the site’s purpose, manually added users is a must.

Maybe I’m missing something….I don’t know. Unfortunately, I need to be able to give some new users the same capabilities as paying customers…I know it probably makes no sense (as it kind of defeats the purpose), but it is needed. Thanks in advance for all of your assistance Christian and any insight you have to helping me come to a solution on this.

• This reply was modified 4 years, 8 months ago by  VegasKev.

Thank you for your response. I understand that s2member doesn’t support that plugin. My question is how do I give certain roles (other than admin) the capability to see the wp-admin dashboard? s2 member is obviously blocking everyone except admin from wp dashboard (which makes perfect sense), but I need to know where this code is, so that I can give that one specific role wp-dashboard access. Thanks in advance.