Problem with diacritics, possibly HTML entity problem.

MarekCifra · 14 January 2025 08:30

Hello. I installed Suite CRM 8.7 on Ubuntu, MariaDb 10.11, Apache 2.4 PHP 8.2
I have problem that some characters are not showed properly. For example “í” is showed like: “í” This is happening on all fields which are TextArea type. When I put same “í” to the TextField it is OK. I download installed wersion of SuiteCRM 8.4 and on this version everithink is fine. But on by installation of 8.7 not. I was looking for diferences but I found nothink. Does anybody know why is that and what to do ? Thanky you. Marek

BastianHammer · 14 January 2025 11:07

Hello Marek,

maybe it’s one of these issues:

github.com/salesagility/SuiteCRM-Core

Descrition field in tasks shows html-entities for special characters

opened 01:40PM - 15 Jul 24 UTC

Porhoken

Type: Bug Priority:Moderate Area: Language Severity: Moderate

### Issue When in detail view of a task, the description field shows special ch…aracters (umlauts, accented etc.) as html-entities. ### Possible Fix _No response_ ### Steps to Reproduce the Issue ```bash 1. Create a task. 2. Have a text in the description field containing special characters. 3. Save task and open detail view - description text is shown with html-entites for special characters. ``` ### Context Happens with "english_us" gui, as well as with installed and activated german language pack. The subject field is not affected! Crosschecked with version 8.6.0 - the issue is not there, only in 8.6.1. Checked the SuiteCRM 8.6.1 online demo - happens there as well! The content in the database is correct (ä,ö,ü), i checked that on my install. Possibly related to #471 and #474, but is a different part of the gui. Umlauts in my gui show fine. ### Version 8.6.1 ### What browser are you currently using? Chrome ### Browser Version 126.0.6478.127 (64 bit) ### Environment Information mariadb, php 8.2.21 ### Operating System and Version Ubuntu 24.04 server, minimal install

github.com/salesagility/SuiteCRM-Core

HTML entities displayed in frontend interface

opened 01:42PM - 02 May 24 UTC

Facyla

Type: Bug Priority:Moderate Status: Team Investigating Area: Language Severity: Moderate

#### Issue Some translated strings appear with the HTML entity (eg. "& # 39 ;",… added space so it displays) instead of the wanted character "'"), at least for the single quote character: examples in the Admin area and in the navigation menu ![image](https://github.com/salesagility/SuiteCRM-Core/assets/286492/9069cddf-bb2c-4c3d-b95e-fb6157d82f46) ![image](https://github.com/salesagility/SuiteCRM-Core/assets/286492/39d9e0d3-fd0a-40d4-a012-7f4fc5062568) #### Expected Behavior The HTML entity should display the relevant character: here a single quote. #### Actual Behavior The displayed text is the actual HTML unicode code: & # 398 ; (added space so it displays) Same behaviour with the html entity code & rsquo ; (added space so it displays) There might be also a buit-in mechanism issue that tries to concert/escape some strings in a common maner, as changing the source string from & # 39 ; to & rsquo ; in the source language files (here in modules/Administration/language/fr_FR.lang.php ) seems to "convert" it to & # 39 ; in the cache file located in cache/prod/pools/ folder). #### Possible Fix - Easiest option would be to use the single quote character instead of html entities in the translation strings. Whether as is, or escaped with an antislash. - If there are good reasons not to use UTF8 and stick to old ISO charmaps, invetigate why the characters are not displayed - which would probably related to an htmlentities call somewhere in the cache generation process. #### Steps to Reproduce 1. Export translations from crowdin 2. Change some strings to replace unicode html entities by named html entities, and also by utf8 characters 3. Package the translation module (ie. zip it) and replace the current translation file with that new one 4. Check how the changed translation render #### Context Navigating through the Admin area after testing upgrades. #### Environment * SuiteCRM Version used: 8.6.0

?

CarstenB · 29 January 2025 09:23

The first one did it for me.

github.com/salesagility/SuiteCRM-Core

Fix #274 - Views Incorrectly Encode UTF Characters as HTML Entities

salesagility:hotfix ← GoryMoon:bugfix_274

opened 11:30PM - 26 Nov 23 UTC

GoryMoon

+6 -35

## Description See the issue #274 for more details about the issue. I identi…fied that when the incorrectly encoded characters showed up the [to_html](https://github.com/salesagility/SuiteCRM-Core/blob/117dd8172793a239f71c91222606bf00677eeb33/public/legacy/include/utils/db_utils.php#L90) function didn't have the `$toHTML` global array so instead used the [htmlentities](https://www.php.net/manual/en/function.htmlentities.php) function causing the html encodings. https://github.com/salesagility/SuiteCRM-Core/blob/117dd8172793a239f71c91222606bf00677eeb33/public/legacy/include/utils/db_utils.php#L99-L102 ~~With the small change of defining the variable in the `$GLOBALS` array, the function will use that and encode it correctly.~~ ~~There might be more related to encoding issues but this fixes my issues and what it looks like the issue is having.~~ See this comment for an update on the changes to this: https://github.com/salesagility/SuiteCRM-Core/pull/403#issuecomment-2312774962 ## Motivation and Context ## How To Test This 1. Change the name of something that is referenced. a. For example, change the company name that is referenced in a Call. (Like adding åäö or other letters) 2. Got the the list of that data and you should see the HTML encoded letters ## 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.