&gt ' apostrophe arrow right being replaced

[NevadaTech]

Hello,
I’ve finally started my official move from SugarCRM 6.2.1. My setup is

• Ubuntu 22.04
• SuiteCRM 8.6.1
  and I getting some issues I’d like resolve.

I’ve used SugarCRM as my ticketing system for a small tech support company for decade(s). Once I upgraded my Proxmox from v7 to v8 SugarCRM died. I imagine the whole Red Hat 5 platform is not supported. The CRM(s) are not accessible from the outside world, only from the LAN by design - I’m paranoid and deal with medical offices (HIPAA) . Accounts are my clients, Cases are jobs at the clients, when a job is technically completed we then toggle the status to Pending Input so my accountant knows to bill the client. While not the perfect solution it has worked well and I control my data.

For this topic, when I use an apostrophe " ’ " in Cases it is replaced by “'” and arrow right “>” becomes " & amp; gt;" How do I change this? Is this a case of the UTF setting? I’m looking for US standard.

Thanks!

[chris001]

FYI Proxmox 8 should let you run a Red Hat 5 platform inside its own fully virtualized “Virtual Machine”, and then Proxmox 8 would only be able to start it, shutdown, reboot it, etc.

Please share the screenshots of where in Cases is Suite showing symbols such as > incorrectly as > the HTML entity name, and ' as ' the HTML entity number.

[NevadaTech]

Here’s an example…
In the first red part I wrote the word then typed the symbol. It saves it in some UTF/code (?) fashion.
In the second red part it is supposed to be 2 right arrows >>

[NevadaTech]

As for RH5 on Prox8, yes, I am sure I can whack at it to make it work. But I’d prefer to move away from the legacy platform. In the short term I moved SugarCRM back to a Prox7 platform until I migrate the important data into SuiteCRM.

[NevadaTech]

It looks like the solution is to turn off TinyMCE entirely. This appears to be an issues since 2015. I’ve seen some solutions for older versions. I’m not sure if they will work in the current release though.

It does strike me odd that I’m having this issue. My setup is amazingly plain-jane. Are there no others with this issue?

Case Description shows HTML <p>

Oddl, I too came across this problem and started to dig around. I have used SuiteCRM 7.1 for my own internal purposes, but now I thought I would use it as a contrived project management tool for each new project I work on. As such I loaded up 7.4 configured it to my liking and was overall pleased with all the new features, except the HMTL problem which creeps up in other areas as well. Since I need it outward facing for my clients, I was horrified when I saw this as I had just created a new ca…

Case Description showing HTML

Hey guys. I have a big issue because when i create a case it shows HTML code… How can i fix this? I prefer use PLAIN TEXT… How can i do this? Thanks!

html tags in the status description in 'cases' module

Please see the attached image. html tags( ) appear in the status description field in the Cases module. Note that this is only happening for few ‘cases’. Others are displaying fine. Can you please help me to resolve this?

[NevadaTech]

Any chance there’s a simple checkbox somewhere that is essentially >>> TinyMCE = off/on

[rsp]

I don’t see such option but yes, even for me it is replacing right arrow & apostrophe with code.

What module is this? >> 8 GB

it's new bug

[rsp]

Add 'nl2br' => true, to module’s public/legacy/custom/MODULE/metadata/editviewdefs.php code.

   4 =>
        array(
          0 =>
          array(
            'name' => 'description',
             'nl2br' => true,
          ),
        ),

[NevadaTech]

I was hoping to turn off the TinyMCE but I’m having no luck.

I did a
find /var/www/html/ -name view.edit.php

which got me to
/var/www/html/suitecrm/public/legacy/modules/Cases/views/view.edit.php

NOTE: there are bunches of view.edit.php files, make sure you are looking as the Cases/views file

the code there generates 3 concerns

• it’s listed as Legacy, any chance it is still active?
• no TinyMCE to REM out
• the only reference I see is include/SugarTinyMCE.php

Should I REM the include line? I cannot find a SugarTinyMCE.php file anywhere. I’m guessing it is buried inside a higher level library (include) file?

Mind you, I don’t do this, like, at all. Give me instructions on what to edit in a file and I’ll do it. That’s completely different from understanding what’s going on and the possible ramifications of the code changes.

<?php
// I cut out the copyright info for this post

require_once('include/SugarTinyMCE.php');

#[\AllowDynamicProperties]
class CasesViewEdit extends ViewEdit
{
    public function __construct()
    {
        parent::__construct();
    }



    public function display()
    {
        parent::display();

        $newScript = '';

        if (empty($this->bean->id)) {
            $newScript = "
                    $('#update_text').closest('.edit-view-row-item').hide();
                    $('#update_text_label').closest('.edit-view-row-item').hide(
);
                    $('#internal').closest('.edit-view-row-item').hide();
                    $('#internal_label').closest('.edit-view-row-item').hide();
                    $('#addFileButton').closest('.edit-view-row-item').hide();
                    $('#case_update_form_label').closest('.edit-view-row-item').
hide();";
         }

         echo '<script>$(document).ready(function(){' . $newScript . '})</script
>';
    }
}

[rsp]

Case Description showing HTML

I know this is a very belated reply but I’ve just ran into the same issue and fixed it by creating a file at /custom/modules/Caes/views/view.detail with the following code: <?php require_once('include/MVC/View/views/view.detail.php'); class CasesViewDetail extends ViewDetail { function display(){ $this->dv->focus->description = html_entity_decode($this->dv->focus->description); parent::display(); } } After making the changes you’ll need to run a repair and rebuild.…

More topics:
https://community.suitecrm.com/search?q=disable%20TinyMCE

[NevadaTech]

Thanks, I’ve seen that post and referenced it for others.

I do see

Email Signatures not formatting correctly

It seems that the problem is part of TinyMCE. It affects the whole body of a plaintext email, not only the signature! The solution seems to be: As of version 3.0a1, forced_root_block is enabled by default. The documentation also saysthat if you disable this option, Enter will produce a <br />, while Shift+Enter will produce a <p>. Try this: tinyMCE.init({ mode : "textareas", theme : "simple", forced_root_block : false, }); Any idea where to find this? Would be good if forced_ro…

which references disabling TinyMCE. It kinda matches my concern that the ‘legacy’ really does mean old/not likely used. The post points to the editing the VARDEFS file now. But I’ve have yet to figure out what to do where.

[rsp]

Search these forums for legacy.module_routing to learn how to change the mode of specific modules.

config/services/module/module_routing.yaml

[NevadaTech]

A possible solution…

How to disable rich text WYSIWYG editor on case description?

Our use case has no need for rich text or a WYSIWYG editor for the description field in cases. How do we stop it from showing up there?

[rsp]

Try it and let us know!

[NevadaTech]

Thanks, but that seems to be going further down the rabbit hole.

[NevadaTech]

Nope.

I tried adding the file …/suitecrm/public/legacy/custom/Extension/modules/Cases/Ext/Vardefs/customizations.php ; after a Quick Repair and Rebuild all it did was brick my interface. Thankfully I took a snapshot first.

It seems like turning off the TinyMCE editor is the fix. Just no idea where to turn it off at. Sigh.

I did reach out to the original fixer to see if he/she has insight for the new platform.

[rsp]

This is for Email:

I forgot to how use

Nevermind I found the solution in one of my very old threads: You have to go to your users profile and change the editor from “Mozaik” to “TinyMCE”: [image] and then hit save of course. However, thanks anyway guys! Kind regards

[NevadaTech]

Thanks, I tried changing it anyway but it had no effect on Cases.

[rsp]

You need to report this bug to SuiteCRM.

Build software better, together