Iām tinkering with SuiteCRM 7.12.5 and Iām trying to enable TinyMCE in Case resolution field, so the resolution can be edited in WYSIWYG way but Iām unable to do it in upgrade-safe way.
When I edit directly /modules/Cases/vardefs.php and add
'editor' => 'html';
for the resolution field array, TinyMCE gets enabled in case resolution field.
Iāve tried extending resolution field through /custom/modules/Cases/Ext/Vardefs but it doesnāt seem to be picked up. Iāve tried creating custom php file (resolution_editor.php) and adding the line to the vardefs.ext.php but none seemed to work.
The line in the php file, as far as I understand, should look like this:
Was playing with this issue this morning, though via the front end at the bottom of profile where there is a dropdown allowing you to chose between direct HTML, TinyMCE and Mozark however it never seems to change from TinyMCE.
Iāll look at confirming this issue, raising a bug if needed and will link here
That profile option only affects the Email Templates module. It really should affect other places, most notably the Email Compose screen, but it doesnāt (I had to add that to my Power Replacer add-on, so I could have pure Direct HTML editing in the compose screen).
I wouldnāt spend to much time on this in 7.12, since it is already much better in v8ā¦
@Mac-Rae Thanks. Itās not that I canāt change to TinyMCE in case resolution description. by default itās a simple plain text field and Iām trying to enable HTML editor in there in a upgrade-safe way
I tried playing with v8 but first I couldnāt get it to install in CentOS and finally managed to get it up and running using Ubuntu Server. And when I finally managed to get it to work it turned out I had a problem with dynamic dropdown lists which werenāt working properly (at least in 8.0.4). Maybe Iāll give it another try, as Iām still just trying to see if Iāll be able to tailor it to my companyās needs.
@blqt OK, Iāll try it tomorrow. I see you suggest to create file inside custom/Extension/modules/Cases, while Iāve been adding it to /custom/modules/Cases. Maybe thatās the reason it didnāt work. Iāll see and let you know.
EDIT: Thanks, it worked! I knew I were doing something worng, it turned out the file needed to be placed in /custom/Extension/modules, like you said, not in /custom/modules/, where Iāve been putting it.