Bug #89231
closedImage data attribute lost in the workspace process
0%
Description
Hello all,
We use the workspace module. When we simulate a user, with a workspace, if we use an image content with attributes (title, alt ...), we lose the attributes when we save. We have to publish the content to be able to save attributes.
We use typo3 V9.5.9.
Thanks for you help,
Xavier
Updated by Riccardo De Contardi almost 5 years ago
- Status changed from New to Needs Feedback
Is this issue reproducible on 9.5.13? Can you add a step-by-step guide?
This is what I saw:
1) Use a draft workspace
2) Go to list module, upload an image
3) Edit the image information and add some informations, like title and caption, save it
4) Go to a page, create a text and image content element
5) Select the image uploaded at point 2)
Results: The title and caption fields are empty.¶
The behavior is different on LIVE workspace: if you repeat the points 1-5 on LIVE workspace, the title and caption values are taken from the ones you entered on the filelist module (and can be overridden of course)
Is this the issue you are experiencing?
Updated by Riccardo De Contardi about 4 years ago
The behavior I described is still present on version 11.0.0-dev (latest master)
In order to make the info from file appear (even in the Draft workspace) you have to publish the file (using the workspace module); alternatively, use a file uploaded and edited in LIVE workspace (In other words: the info from LIVE workspace are considered)
Updated by Riccardo De Contardi about 4 years ago
Updated by Benni Mack almost 3 years ago
- Related to Bug #77917: Can't save image metadata in a translated content element in draft workspace added
Updated by Benni Mack almost 3 years ago
- Related to Bug #82954: Unable to save data in translations of sys_file_reference records in workspace added
Updated by Riccardo De Contardi about 2 years ago
As far as I can see this is still reproducible on 12.0.0-dev (latest main)
Updated by Riccardo De Contardi 7 months ago
As far as I can see this is still reproducible on 13.1.0-dev (latest main)
Updated by Georg Ringer 4 months ago
- Status changed from Needs Feedback to Closed
closed in favor of #82954
bug is not yet fixed