View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007622 | module Visual CMS | module Visual CMS - sub | public | 2024-03-20 16:22 | 2025-10-02 13:26 |
| Reporter | CSDev | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.2.2 | ||||
| Fixed in Version | 9.0.0 | ||||
| Summary | 0007622: Text copied from MS word into VCMS widgets leads to shop crash | ||||
| Description | The user receives translated texts in MS Word. He copies these in whole or in part into VCMS widgets. The formatting of MS Word is so extensive that the formatting tags that VCMS normally applies can no longer be closed at the end. After saving the VCMS element, the shop crashes and the user has no way of accessing the VCMS element in the backend. The element is no longer displayed. Instead, it must be deleted from the database. | ||||
| Steps To Reproduce | Copy formatted text from MS Word into for e.g. VCMS widget TEXT and save. | ||||
| Additional Information | The faulty VCMS element should not be rendered. It must be possible to delete it in the backend. | ||||
| Tags | No tags attached. | ||||
|
|
For your information, in OXID 7 the database field is increased to MEDIUMTEXT: 16,777,215 (224?1) bytes = 16 MiB This at least reduces the occurrence. Nevertheless, I cannot reproduce a shop crash. Only if you open the affected CMS content in the frontend, you get a maintenance mode. The rest of the shop continues to work. In Visual CMS, content is no longer displayed in the affected CMS content, but it can be repopulated by creating a new widget. It is also possible to delete all widgets with the button at the top right or to delete the CMS content completely with the button at the bottom left, next to the Save button. Editing in the database is therefore not necessary. |
