The Yoast SEO plugin overrides Access rules

Won't fix

Reported for: Toolset Access 2.2.2

Symptoms

Yoast SEO plugin can override the rules you set for your custom user roles using Toolset Access.

The following steps represent an example when this happens:
1. You create a custom user role and copy the rights for it, from the Guests role.
2. In Access, you give the Post edit rights to your custom user role.
3. If the Yoast SEO plugin is active, users belonging to your custom role will still not be able to see the Posts and Tools links in the main WordPress menu.

Please note that this conflict is coming from the Yoast SEO plugin and not Access. However, it is not a bug in itself, but simply the way Yoast SEO handles the edit_posts capability.

Workaround

There is a simple solution to this issue:
1. Go to Toolset -> Access Control and click the Custom Roles tab.
2. Click the Change permissions link for your custom user role.
3. In the dialog box that opens, click Custom capabilities.
4. Put edit_posts as both the Capability name and Capability description

Adding a custom capability "edit_posts"
Adding a custom capability “edit_posts”

4 thought on The Yoast SEO plugin overrides Access rules

  • Hello Bleery.

    The first step of the example says “1. You create a custom user role and copy the rights for it, from the Guests role.”

    Hence, it is the array of rights of the Guest role, that is the basic issue here.

    Only by “Put edit_posts as both the Capability name and Capability description” (Custom Capability) this is solved.

    This should be the same behavior for Guests, hence, since the Custom Role just inherited the Guest role, correct?

    Concluding, if I misunderstood your comment, it would be helpful for me (so to help you more effectively) if you could open a support thread with this problem.

    Please acknowledge that this issue here describes a problem tightly related to YOAST plugin. If you disable YOAST all issues should be resolved. If this is not the case, it would be another, new issue, that I do not yet know of.

    The best in any case, if the issue remains visible for you despite above information – would be to report this to us in our Support Forum, if this is possible.

    Thank you

Leave
a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>