#106193JavaScript table wizard in TYPO3 table content element breaks cell values
Description
In the content element “table” the JavaScript table wizard has two issues:
- Changes to
table_delimiterandtable_enclosureare not recognized immediately and taken into account on next save of the content element - Using the delimiter also in a cell value gets the cell value displayed in two cells instead of one after next save
How to reproduce # 1:
- Create a table content element
- Default value for
table_delimiteris “Pipe” andtable_enclosureis “none” - Set
table_delimiterto Comma andtable_enclosureto “Double quotes” - Enter
foo,barinto a cell - Save the content element
Result:
fooandbarare displayed in different cells- In the database the field
bodytextis filled withfoo,bar
Expected behaviour:
- The Wizard shows only one cell with
foo,bar - In the database the value is stored with
"foo,bar"
Next step:
- Change
footofoo2 - Save the content element
- The bodytext DB field is now correctly filled with
"foo2","bar"
How to reproduce # 2:
- Create a table content element
- Set
table_delimiterto Comma andtable_enclosureto “Double quotes” - Save the element without entering data into any cell!
- After save, enter
foo,barinto one cell and save
Result:
fooandbarare displayed in separate cellsbodytextfield in database is saved withfoo,bar
Expected behaviour:
- The Wizard shows only one cell with
foo,bar - In the database the value is stored with
"foo,bar"
Next step:
- Change the value of one cell and save
- Now
bodytextis correctly saved with"foo2","bar"
Further observations:
- The frontend rendering is correct for what is stored in the
bodytextdatabase field - If you only fill
bodytextaccordingly, e.g. by making direct changes in the database, the frontend output also functions correctly - The data in the database only breaks when you use the wizard and save the content element
I assume that # 2 can be fixed within writeTableSyntaxToTextarea() in Build/Sources/TypeScript/backend/form-engine/element/table-wizard-element.ts
For # 1 I have no idea so far.
Unfortunately I’m not good in JavaScript to provide a patch.
Reviews 1
Related issues 1
History 13
-
Peter Kraume changed Related to #106917 <span data-processor="relativetime" data-value="2025-06-20T17:49:29+00:00" > 06/20/25, 17:49 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 91625 status
NewUnder Review <span data-processor="relativetime" data-value="2025-11-13T16:21:54+00:00" > 11/13/25, 16:21 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91625 <span data-processor="relativetime" data-value="2026-04-22T06:42:39+00:00" > 04/22/26, 06:42 </span>