HTML view at knowlege base

danielrios · 7 November 2024 07:48

We update to SuiteCRM 8.7.1 and we are getting problems with knowledge base, we see the content with HTML tags [html] How we have to do to read correctly the content ¿??

rsp · 7 November 2024 14:26

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

danielrios · 7 November 2024 14:59

The problem/error is not solved with this:

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

and the other link is about other diferente error…