At the moment, TinyMCE uses the profile assigned to the lowest role ID that a user is a member of. This means that if you assign a basic profile to the authenticated user role and a more powerful profile to a more privileged role, users who are members of both roles will see the profile assigned to the authenticated user role.
I thought about reversing this and showing the profile assigned to the highest role ID that the user is a member of, but roles are not always added in order from least privileged to most privileged. So a way of specifying the priority of profiles is needed.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | tinymce.install.profile_priority.diff | 1.51 KB | OliverColeman |
| #13 | tinymce.module.profile_priority.diff | 5.15 KB | OliverColeman |
| #2 | tinymce_7.patch | 7.05 KB | darren oh |
| #1 | tinymce_6.patch | 5.59 KB | darren oh |
Comments
Comment #1
darren ohHere is a patch to allow profiles to be prioritized.
Comment #2
darren ohI missed an SQL query that needed to be changed. Also added an update to the install file.
Comment #3
m3avrck commentedHow does that compare to? http://drupal.org/node/60667
Like to see a consensus before this goes in.
Comment #4
pwolanin commentedWhy not simply do it in reverse role ID order, and then hook into the role weights module (if it's installed) if additioanl control is needed?
Comment #5
darren ohIt was considered, but there was no logical relation between role ID and privilege levels on sites with multiple roles.
Comment #6
flanderz commented+1 for this approach
Comment #7
flanderz commentedLet me clarify ... +1 for the approach that Darren is suggesting.
Comment #8
darren ohAlternative patches are available in duplicate issue 60667.
Comment #9
femrich commentedI look forward to seeing this implemented (without patching) in a stable release of TinyMCE. Any idea when that might happen?
Comment #10
theorichel commentedAnd I would very much that the specialists would come to an advice whoich patch we ought to use now, while waiting, waiting for Tiny MCE to solve it finally. I have read the debate and I do not know what to do now.
Thanks
TR
Comment #11
Sophia commentedSubscribing!
Comment #12
husztisanyi commentedhttp://drupal.org/node/181798#comment-792447
Comment #13
OliverColeman commentedHere's a remake of the patch in #2 for 5.x-1.9