View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006602 | OXID eShop (all versions) | 2.3. Extensions (modules, themes) | public | 2017-03-09 12:53 | 2017-06-23 10:31 |
Reporter | [email protected] | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Platform | Linux | OS | RHEL | OS Version | 6 |
Product Version | 4.10.3 / 5.3.3 | ||||
Summary | 0006602: Visual CMS JS Language Translation broken | ||||
Description | When your shop is in utf-8 mode and you have a module installed which has a language file in ISO-8859-1 encoding then the javascript translations in the Visual CMS Module are broken because the JSON response is always false. This is because the module itself tries to json_encode an array with data which is not utf-8 encoded and therefore returns false. This produces also a javascript error in the firefox console. | ||||
Steps To Reproduce | 1. Activate a Module with ISO-8859-1 Language file. 2. Set utf8 Mode in config.inc.php to 1 3. Activate Visual CMS Module. 4. Add any widget. 5. Remove a the widget. 6. You will see the broken language translation like DD_CONFIRM. | ||||
Additional Information | Problem is in the ddoeVisualCmsOxUtils class. Look for the encodeJson function. This is called from the ddoeVisualCmsLangJs class. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Theme | All | ||||
Browser | All | ||||
PHP Version | 5.6 | ||||
Database Version | 5.6 | ||||
|
The issue is not reproducible in a standard shop. It was tested in OXID eShop 4.10.3. The following steps were followed: 1. New Module "Mod1" with <ShopURL>/modules/Mod1/translations/de/file_lang.php encoded in ISO-8859-1 2. Activated Module "Mod1" 3. utf8 Mode in config.inc.php was by default set to 1 4. Activated Visual CMS 5. Added + Removed a widget. There was no problem with translations. (Check DD_confirm.PNG) Can you elaborate on "JSON response is always false". Under "Additional Information" it is mentioned that the problem was in ddoeVisualCmsOxUtils class. Can you please give an example or workflow how the translation in another module affects the visual cms translations? |