| User | Post |
|
1:32 am
May 27, 2011
|
quimic
Member
| | Paris (France) | |
|
| posts 11 |
|
|
Hi,
I have this issue that I believe is a bug, but I am not sure. I am using v1.3.39, on a 3.1.2 WP multisite install, and the same problem occurs on all blogs within the network.
My Editor users cannot edit categories or tags. When they click on a category / tag in the admin screens (or on the Edit Category / tag button in the top admin bar), they get a blank screen with the message "Cheatin' hu?"
But they can in fact modify a category / tag using the quick edit button instead of Edit. They also can add new ones but cannot delete them ("You do not have permission to do that" message).
I really tried to check every option to figure out where this right limitation could come from, but could not find it.
I did notice though that in the WP / RS Role Equivalence, the Editor does not show the "manage categories" capability. I tried to add "category manager" (and "category assigner") capability to the "WP Editor" through the roles / categories screen without success.
Any idea?
|
|
|
9:15 am
May 30, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
Thanks for letting me know. Role Scoper 1.3.35 introduced a bug preventing non-Administrators from editing categories / tags if "Link Categories" are enabled for RS filtering. This is fixed in the updated Role Scoper development code (1.3.40-dev).
If your WP / RS Role Equivalence table does not show "Category Manager" as a contained role for "Editor", you may have customized your category management capability. In that case you will need to either change it back to "manage_categories", use a WP role editor to add that capability to the "Editor" role, or go to Roles > General and assign the "Category Manager" role to the group [WP Editor].
|
|
|
1:30 am
May 31, 2011
|
quimic
Member
| | Paris (France) | |
|
| posts 11 |
|
|
Thank you.
I am currently testing, and I'll let you know how it goes.
|
|
|
2:51 am
May 31, 2011
|
quimic
Member
| | Paris (France) | |
|
| posts 11 |
|
|
Ok, so your corrections seem to have fixed the major issues for categories, but not for tags (still getting the "cheatin'" message).
There is also a plugin interaction categories bug with the WPML multilingual management plugin:
With this plugin, categories/tags are translated. So, when you edit a post, you see only categories corresponding to the current post's language.
When editing a post as editor, this does does work. In the post edit window, you get a php warning in the category selection box ("Illegal offset type in isset or empty" in the WPML plugin source), and see all categories in all languages.
Using an admin role or deactivating Role Scoper makes WPML behave normally (you see only the categories corresponding to the current language).
Thanks in advance for your help.
|
|
|
5:44 am
May 31, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
quimic said:
Ok, so your corrections seem to have fixed the major issues for categories, but not for tags (still getting the "cheatin'" message).
This is already fixed in the Role Scoper development code. It's not a configuration issue.
|
|
|
6:50 am
May 31, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
quimic said:
There is also a plugin interaction categories bug with the WPML multilingual management plugin:
With this plugin, categories/tags are translated. So, when you edit a post, you see only categories corresponding to the current post's language.
When editing a post as editor, this does does work. In the post edit window, you get a php warning in the category selection box ("Illegal offset type in isset or empty" in the WPML plugin source), and see all categories in all languages.
Using an admin role or deactivating Role Scoper makes WPML behave normally (you see only the categories corresponding to the current language).
Thanks in advance for your help.
WPML recently went to a new term filtering mechanism. The Role Scoper development code (1.3.40-dev) is now updated to deal with that.
|
|
|
8:33 am
May 31, 2011
|
quimic
Member
| | Paris (France) | |
|
| posts 11 |
|
|
I just downloaded and installed the dev version again. I confirm that the WPML issue is now fixed, but not the tags issue.
Editors still get the "cheatin" message , as they did with categories before the fix.
|
|
|
10:09 am
May 31, 2011
|
Kevin
Admin
| | | |
|
| posts 2503 |
|
|
quimic said:
I just downloaded and installed the dev version again. I confirm that the WPML issue is now fixed, but not the tags issue.
Editors still get the "cheatin" message , as they did with categories before the fix.
Ironically, it was working if "Post Tags" are enabled for RS filtering (under Roles > Options > Realm), but not if disabled.
This is fixed in the newly updated Role Scoper development version (1.3.40-dev).
|
|
|
10:37 am
May 31, 2011
|
quimic
Member
| | Paris (France) | |
|
| posts 11 |
|
|
Login
Register
Search 
Forums
Topic RSS 