Just upgraded from version 7.14.8 to 7.15.0 - Email body window missing?

PowerQuest · 12 January 2026 16:41

Hello!

So i just ran the upgrade on our CRM instance and now the whole body text window is gone and basically blank so you cannot type anything at all. See screenshot below:

Also I have always in the past tweaked the EmailsComposeView.js to add more tools on the editor but that has changed too ind the code so you cannot do that anymore?

New code after upgrade:
$.fn.EmailsComposeView.defaults = {
“tinyMceOptions”: window.emailTinyMCEConfig
};
}(jQuery));

Old code:
$.fn.EmailsComposeView.defaults = { "tinyMceOptions": { /* add plugins */ // plugins: "fullscreen", plugins: 'code print preview fullpage searchreplace autolink directionality visualblocks visualchars fullscreen image link media template codesample charmap hr pagebreak nonbreaking anchor insertdatetime advlist lists textcolor wordcount imagetools contextmenu colorpicker textpattern', /* */ menubar: true, toolbar: ['fontselect | fontsizeselect | formatselect | bold italic underline strikethrough forecolor backcolor | image | alignleft aligncenter alignright alignjustify | styleselect | bullist outdent indent | removeformat | numlist | link | unlink | undo | redo | copy | paste'], formats: { bold: {inline: 'b'}, italic: {inline: 'i'}, underline: {inline: 'u'} }, convert_urls: true, relative_urls: false, remove_script_host: false, } }; }(jQuery));

So how do you configure the TinyMCE tools then?

and two; how can the issue with the email body text window be fixed?

Thanks in advance

Kind regards

rsp · 12 January 2026 16:47

Go to profile and scroll down to bottom.

Check your editor.

You could also check in the config.php file.

PowerQuest · 12 January 2026 17:37

But that doesn´t resolve the issue with the body text field is missing?

Could you specify what to look for?

Thanks.

rsp · 12 January 2026 17:50

Sorry, we do not have anything in config.

You can go to studio-> Email and try to reset to default. Maybe it will fix it.

Looks good in demo.

pgr · 12 January 2026 18:04

I am not sure, but I would try changing it here

include/SugarTinyMCE.php

and then aggressively rebuild, repair, restart, refresh, etc

pstevens · 12 January 2026 19:45

I had the same problem. Its just a browser cache and/or SuiteCRM cache issue. I had Shift F5, multiple times on any page that had the TinyMCE both before and after it opens.I also did this:

rm -rf cache/js/*
rm -rf cache/themes/*
rm -rf cache/smarty/*

PowerQuest · 13 January 2026 12:50

Thanks for the reply @pstevens and @pgr .

So i got some questions because I was after updating yesterday “I was caught with my pants down” because I just expected regular update process with no huge changes.

Oh boy I was wrong!

Fortunately I had taken a full backup before updating (I always do that), so I could revert our SuiteCRM instance back to a working state so we could continue the production. But this is obviously not long term viable solution, but a quick fix as I need need to update our CRM system.

I just need to get it right this time!

We do not use any external caches /CDN’s on our CRM Intentionally as I don’t want it to be cached since SuiteCRM generates somethings on the fly dynamically.

So with that said, educate me like I was 5 years old and tell me please…

1.) So after you did the upgrade like me yesterday. Did you like PGR

also rebuild everything in admin?
Which repair functions did you use (I’m asking because there is a TON of repair options in admin UI), could you please tell me which are the relevant ones in this case?

After you done that did you then clear the cache:

manually? ANy other step you did to get your CRM up and running normally again too?

2.) So this update seems pretty change and “life” changing in that the whole tinymce has been moved from the current old location (modules/Emails/include/ComposeView/EmailsComposeView.js) to user UI in the profile where each user can set his own “tools” preferences?

3.) Have the location of the file responsible for the listed number of “favorites” and “recently viewed leads” been changed too? E.g. “_headerModuleList.tpl“ usually located at:
custom/themes/SuitePImproved/tpls/_headerModuleList.tpl
where you change the number 6 and increase it to your preferred number (in my case 15):
{if $smarty.foreach.lastViewed.index < 12}

Is there other huge changes in this critical update that I need to be aware of by the way?

Thank you so much guys!

Kind regards
PowerQuest

pstevens · 13 January 2026 14:36

From my perspective (I’ve been using it for about a week now). This was one of the easiest, least problem updates I’ve ever done. Especially with all the major changes, I was expecting lots of problems. Other than the cache issue with the TinyMCE, everything else is working great. The TinyMCE wasn’t really a big issue as I’ve experienced this before the last time they upgraded it. I’d suggest the following, I don’t know exactly which one will solve it for you:

Do ALL the repairs and rebuilds. Espeically the JS ones
Delete the cache folders I’ve shown already.
SHIFT F5 everywhere, multiple times wherever you see the TinyMCE, before and after popups that contain it as well.

This has worked for me in the past, and worked for me in this case.

rsp · 13 January 2026 14:39

Check out the release notes of v7.15

For v8.9.2,

github.com/SuiteCRM/SuiteCRM-Core

Fix #797 - Default Email Template Editor incorrect

hotfix ← jack7anderson7:fix/797

opened 08:07AM - 10 Dec 25 UTC

jack7anderson7

+2 -2

## Description Fix #797 ## Motivation and Context Fix #797 ## Ho…w To Test This See #797 ## Types of changes - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Final checklist - [X] My code follows the code style of this project found [here](https://docs.suitecrm.com/community/contributing-code/coding-standards/). - [ ] My change requires a change to the documentation. - [X] I have read the [**How to Contribute**](https://docs.suitecrm.com/community/contributing-code/) guidelines.

PowerQuest · 13 January 2026 15:51

Thanks!
How did you solve the issue I have with adding custom options to the tool bar, (If you have custom stuff like me)?

Is the last viewed lead and favs the same or it has changed too?

Thanks a bunch again.

pstevens · 13 January 2026 16:04

I don’t have any custom options in the toolbar. I don’t see the favorites or anything working any differently than they did before in the sidebar on my install. However, I don’t use them that much so nothing pops out to me as having changed.

PowerQuest · 14 January 2026 08:35

Thanks for answer @pstevens

Kind regards

PowerQuest · 28 January 2026 03:54

Well I think I solved it.

In my case there was a directory and file permission issue with the newly added files/folders from the update. So i reset them to755 / 644.

I haven’t figured out the last part with favs/last viewed and adding/editing tools to the TinyMCE. But I guess I get there sooner or later when I find time for it. At least SuiteCRM is now updated to latest version.

pstevens · 29 January 2026 21:33

I did find in the knowledge base there is a reference to the old tiny mce. Not sure if this is evident elsewhere in SuiteCRM, but changing the value in the custom editviewdefs.php fixes:

Replace the old include:

'file' => 'include/javascript/tiny_mce/tiny_mce.js',

with the new path:

'file' => 'vendor/tinymce/tinymce/tinymce.min.js',

PowerQuest · 30 January 2026 18:59

Thanks!
But could you kindly enlighten me what is the actual server path to that file (editviewdefs.php), as there is several of them named “editviewdefs.php“

Thanks in advance.
Kind regards

rsp · 30 January 2026 19:13

@pstevens @PowerQuest found these code files related to it.

AOK_KnowledgeBase

github.com/SuiteCRM/SuiteCRM

modules/AOK_KnowledgeBase/metadata/editviewdefs.php

hotfix


      
            array(
              'label' => '10',
              'field' => '30',
            ),
            1 =>
            array(
              'label' => '10',
              'field' => '30',
            ),
          ),
          'includes' =>
          array(
            0 =>
            array(
              'file' => 'vendor/tinymce/tinymce/tinymce.min.js',
            ),
          ),
          'useTabs' => false,
          'tabDefs' =>
          array(
            'DEFAULT' =>

EMAILs

github.com/SuiteCRM/SuiteCRM

modules/Emails/metadata/composeviewdefs.php

b2f9811e2


      
                      array('customCode' => '<button class="vertical-separator"></button>'),
                      array('customCode' => '<button class="btn btn-save-draft" title="{$MOD.LBL_SAVE_AS_DRAFT_BUTTON_TITLE}"><span class="glyphicon glyphicon-floppy-save"></span></button>'),
                      array('customCode' => '<button class="btn btn-disregard-draft" title="{$MOD.LBL_DISREGARD_DRAFT_BUTTON_TITLE}"><span class="glyphicon glyphicon-trash"></span></button>'),
                  )
              ),
              'includes' => array(
                  array(
                      'file' => 'modules/Emails/include/ComposeView/EmailsComposeView.js',
                  ),
                  array(
                      'file' => 'vendor/tinymce/tinymce/tinymce.min.js'
                  ),
                  array(
                      'file' => 'include/javascript/qtip/jquery.qtip.min.js'
                  )
              ),
          ),
          'panels' => array(
              'LBL_COMPOSE_MODULE_NAME' => array(
                  array(
                      array(

AOS_PDF_TEMPLATES

github.com/SuiteCRM/SuiteCRM

modules/AOS_PDF_Templates/metadata/editviewdefs.php

b2f9811e2


      
              1 =>
              array(
                  'label' => '10',
                  'field' => '30',
              ),
          ),
          'includes' =>
          array(
              0 =>
              array(
                  'file' => 'vendor/tinymce/tinymce/tinymce.min.js',
              ),
              1 =>
              array(
                  'file' => 'modules/AOS_PDF_Templates/AOS_PDF_Templates.js',
              ),
          ),
          'useTabs' => false,
          'tabDefs' =>
          array(
              'DEFAULT' =>

pstevens · 30 January 2026 20:05

My issue “I think” was that I had customized the layout in studio, so I had a /custom/ metadata file for knowledge base and the custom file did not get updated to the new tiny mce. Fixing that one line solved the problem. Other modules didn’t seem to be a problem. I think some of the older modules that used the wysiwyg by default had this line (my guess) and it got copied over to /custom/ at some point in the past as I’ve been using this install for years.