TinyMCE Profiles (which allow to configure different user profiles based on the roles) are not accessible from WYSIWYG module. Instead, WYSIWYG module provides its own profiles that are related to Input Formats.
The problem that I have appears with Input Formats permissions when trying to access the node from role which is not allowed in the Input Format. Here is the example.
(Role – Input Filter)
Editor – Simple TinyMCE (less buttons)
Moderator – Advanced TinyMCE (more buttons)
In the node we want to allow Editor to see ONLY his buttons and we want to prevent switching to any other Input Format. Same applies to Moderator.
Input filters may be configured using Better Formats module. We can assign Input Format by node and by role, so for ‘Page’: Editor will have ‘Simple TinyMCE’ format and Moderator – ‘Advanced TinyMCE’ format; for 'Story': Editor – ‘Site defaults’ and Moderator – ‘Advanced TinyMCE’ etc.
And here is the problem.
Each node can have only 1 Input Format assigned (which is logical). For example, it has ‘Simple TinyMCE’ assigned. Editor will see his configuration of TinyMCE (as it supposed to be), but Moderator will see ‘Simple TinyMCE’ as well instead of configuration inside ‘Advanced TinyMCE’.
We can try to do in the opposite way. Assign node with ‘Advanced TinyMCE’ Input Format so Moderator will see his required configuration, but despite the fact that Editor’s configuration will be “lowered” by the Better Formats module to his ‘Simple TinyMCE’ Input Format (what is acceptable for us), Editor will have no access to the page as Editor is not allowed to use ‘Advanced TinyMCE’ Input Format.
I’d like to know whether it is possible to use TinyMCE profiles (like in TinyMCE module) within WYSIWYG module OR inbuilt role-based profiles for editor configuration as sub-profiles of each Input Format?
Comments
Currently, there is only one
Currently, there is only one profile per format, and the settings of that profile are fixed.
So what you're saying is; You know a role is trying to break the rules by editing fields with a format they are not allowed to use, but you want to let it do that anyway?
If a Moderator has changed the input format to Advanced, Editors are denied access because they could potentially input content only Moderators are allowed to put there.
The Better Formats module can not "lower" configurations or figure out which format to switch to in order to both let an Editor access it, and keep all 'extended' content potentially added by the Moderator. Core and Better Formats can only set restrictions on who gets to use certain input formats (and thus edit nodes using them) and a user's default format for new nodes (the format their highest priority role has been assigned as default).
If the purpose of the Moderator role is to be able to alter or remove what the Editors have created, so they don't write something offensive or ignore guidelines etc, then both roles should save the node using the same format.
Input formats are there to limit what can be input, not how it's being input or what the GUI looks like. We do understand that sometimes you might want to use a different theme or setting for the edtor without affecting whihc input format is being used. Using two identical input formats and assigning different looking editor profiles to them is probably not practical in the long run. You'll soon end up with lots of content using one of several input formats, which all need to be kept in sync, or content will begin to disappear as formats are changed.
For Wysiwyg 3.x, we do want to allow a many to one relationship between profiles and their input format. Then you could set up lots of editor variations for a single input format. Just note that even if the editor does not have a 'Bold' button in one of those profiles, the user can still make text bold by editing the source and have it show up in the viewed node if the filter allows it. The reverse is also true, some profiles might have a Bold button, but no text will be bold in the viewed node.