The links that are limited to admin, editor, author roles are being revealed to all logged in users since the upgrade to WordPress 3.0
The links that are limited to admin, editor, author roles are being revealed to all logged in users since the upgrade to WordPress 3.0
Likewise
They're working fine for me.
Newest version will user capabilities instead of levels.
v2.2.13 still does not work properly e.g.
<a title="editor+ role" href="http://saltaire-aa.org/news/wp-admin/edit.php?post_type=page">Pages</a>|publish_pages<a title="editor+ role" href="http://saltaire-aa.org/news/wp-admin/edit.php?post_type=page">Pages</a>|true|publish_pages<a title="editor+ role" href="http://saltaire-aa.org/news/wp-admin/edit.php?post_type=page">Pages</a>|true |publish_pagesYour correct - just submitted a fix. Hopefully this will put an end to the issue. Consolidated both of those rules - so now you just need:
|true = for admin
|capability = for any capability
Let me know if that sorts it for you.
That seems to be working fine now
If I understand correctly...
"http://www.mydomain.com/wp-admin/">Dashboard|true"
will show Dashboard link only for admin
If il write...
"http://www.mydomain.com/wp-admin/">Dashboard|editor"
will show Dashboard link only to editor
If il write...
"http://www.mydomain.com/wp-admin/">Dashboard|true|editor"
will show Dashboard link only to admin and editor
@zuzzurro
since v2.2.14
1 - correct
2 - use capabilities instead use examples below
3 - is an unnecessary duplication of tautology in v.2.2.13 it was afflicted by a bug and only allowed admin.
<a href="http://example.com">link</a> | manage_links
or
<a href="http://example.com">link</a> | publish_pages
anyone who has the capability - by default editor has both of these, as does admin
for author you could use
<a href="http://example.com">link</a> |publish_posts
for contributor you could use
<a href="http://example.com">link</a>|edit_posts
the only way of hiding a link from an editor would be to give a capabilty to an author and NOT to an editor eg a custom capability based on say, membership of a special interest group. By default the set of capabilities for an author is a subset of the capabilities of an editor without any capabilities in an excluded set, and admin has them all, since even if a capability is not set for admin he/she has manage_roles (which is a custom capability defined by the role manager plugin) and can give themselves a capability
This topic has been closed to new replies.