3 Comments


  1. It’s best to handle this sort of thing by capability rather than role anyway. Even if you wanted to do a pretty interface for regular folks, you could add something like an rda_admin_access capability for the roles that are allowed. You’d just code that behind the scenes. It’d actually be pretty simple:

    The UI would be a list of all [editable] roles with checkboxes next to them. These checked roles would have access.

    On save/update settings, you grab all roles. For the selected roles, add the custom capability. For unselected roles, check if they have the capability and remove it if they do.

    On plugin activation, auto-add the capability to roles like Administrator, Editor, Author, and Contributor or just the Administrator.

    Doing it this way would make it so much better because it’d be easy for people who do use plugins like Members to create custom roles and have it play nicely with this plugin. They can even manage access from within Members if they were already on the role-editing screen. I need to write more tutorials in this area. Now, I’ll stop thinking out loud and go build something.

    Reply

    1. Great news Justin if you’re going to Build something. But your plugin Members is already awesome. Perhaps more advanced.

      Reply

  2. Hi Jeff, thanks for the mention.

    After activating the plugin, I found it difficult to locate where the configuration settings are. The settings are at the bottom of the Settings > Reading page.

    In v1.0, it had its own settings page, and sticking the options in > Reading for 1.1 was a bit of an experiment. When 4.0 rolls out, I’m probably gonna release 1.2 which should add Multisite support, and based on feedback I may re-introduce the standalone settings screen.

    Reply

Leave a Reply