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.

Comments

darren oh’s picture

Assigned: darren oh » Unassigned
Status: Active » Needs review
StatusFileSize
new5.59 KB

Here is a patch to allow profiles to be prioritized.

darren oh’s picture

StatusFileSize
new7.05 KB

I missed an SQL query that needed to be changed. Also added an update to the install file.

m3avrck’s picture

How does that compare to? http://drupal.org/node/60667

Like to see a consensus before this goes in.

pwolanin’s picture

Why 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?

darren oh’s picture

It was considered, but there was no logical relation between role ID and privilege levels on sites with multiple roles.

flanderz’s picture

+1 for this approach

flanderz’s picture

Let me clarify ... +1 for the approach that Darren is suggesting.

darren oh’s picture

Status: Needs review » Closed (duplicate)

Alternative patches are available in duplicate issue 60667.

femrich’s picture

Version: 5.x-1.x-dev » 5.x-1.9

I look forward to seeing this implemented (without patching) in a stable release of TinyMCE. Any idea when that might happen?

theorichel’s picture

And 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

Sophia’s picture

Subscribing!

husztisanyi’s picture

OliverColeman’s picture

Here's a remake of the patch in #2 for 5.x-1.9