Make a quick vote šŸ—³ ļøHow do you refer to SuiteCRM extensions: add-ons or plug-ins? Click here to have your say šŸ‘ˆ

7.12.6 Email Compose Body is Missing

SuiteCRM Forum - English Language Installation & Upgrade Help
#1

I just upgraded to 7.12.6 from 7.12.4 and when going into Compose Email the body field is missing.
Before the upgrade the emails working perfect - now we have no body field.

CRM_Email_body
CRM_Email_body867Ɨ408 7.64 KB

I found in the history, this problem already exist in version 7.11.16 - but solved in Oct. 2020.
Any idea?

#2

Can you please try deleting a few things from your server-side cache? I saw this problem myself, and I think that is how I solved it, but Iā€™d like to make sure.

Can you please try deleting these two files in your server and see if anything changes?

cache/smarty/templates_c/%%D1^D15^D1540D1D%%ComposeView.tpl.php (the codes will be different but the Composeview.tpl.php part should be there)

cache/themes/SuiteP/modules/Emails/ComposeView.tpl

#3

I deleted those file, but nothing changed. As soon I open the crm in Browser, those files a generated new by the system. The body for the mail composer is still not here.

#4

The point of deleting the files was precisely to ensure that they were regenerated.

But since it didnā€™t fix the problem I donā€™t know what else to tryā€¦

#5

did you try to inspect element and see if there is something missing there?

#6

have the same Problem (only with Edge and Chrome Browser).

Text body missing in e-mail with MS Edge and Google Chrome - SuiteCRM Forum - English Language / SuiteCRM General Discussion - SuiteCRM

#7

Thereā€™s definitely a bug here.

Is any of you coming from an older installation that still had the SuiteR theme? If so, can you please check any mentions of SuiteR in config.php and config_override.php, and change them to SuiteP?

And you can also delete everything from cache/themes/SuiteR.

#8

To be honestā€¦ I am not the hard coder (more an advanced user). Which elements I have to compare with?

#9

Hi,

Follow this step to step process, it should do the trick.

If you have any other requirements around SuiteCRM you can always head over to our website for a free consultation SuiteCRM Solutions | Rolustech

#10

I started from Version 7.11 and checked if there is any waste from SuiteR Theme - nothing foundā€¦

#11

@StefanL did you check all the logs?

  • suitecrm.log
  • php_errors.log
  • browser javascript console

Are you a developer? Can I give you a list of steps involving changes to PHP code?

#12

This solution is from Oct 2020 and doesnā€™t work. The Codes are different with 7.12.6.

  • SugarFieldWysiwyg.php is complete different
    -_head.tpl is already changed in the installation
#13

If anyone really wants to debug this I suggest the following.

Go here: SuiteCRM/SugarFieldHandler.php at master Ā· salesagility/SuiteCRM Ā· GitHub

And change those lines

        } else {
            $string = $field->$displayTypeFunc($parentFieldArray, $vardef, $displayParams, $tabindex);
        }

to add some logging:

        } else {
            $c= New \ReflectionClass($field);
            $f= $c->getMethod($displayTypeFunc)->getFileName();
            $GLOBALS['log']->fatal('SugarFieldHandler.php: vardef is ' . $vardef['name'] . ' of type ' . $vardef['type'] . ' at ' . $f);
            $string = $field->$displayTypeFunc($parentFieldArray, $vardef, $displayParams, $tabindex);
        }

Now, between each test you have to go and delete some cached tpls:

cache/smarty/templates_c/%%D1^D15^D1540D1D%%ComposeView.tpl.php (the codes can be different but the Composeview.tpl.php part should be there)

cache/themes/SuiteR/modules/Emails/ComposeView.tpl (if it exists, but probably it wonā€™t)
cache/themes/SuiteP/modules/Emails/ComposeView.tpl

Then, visit the Compose window once and you will see messages in the logs explaining which files were used for each SugarField. The ones you are interested in are description and description_html. Tell me what you find.