Bug #59910
closed
Editing an image in a draft workspace corrupt the live frontend.
0%
Description
Connected to issue #48464.
Tested in version 6.2.3:
- Start with an existing "text & images" content element with at least 1 image.
- Switch to DRAFT workspace, replace the image.
- Do NOT publish the change.
- Now, in the live frontend, the NEW image is now shown! And not once but TWICE! Despite not having published the change.
The editor/admin can only "repair" this behavior by deleting the content element from the draft workspace.
In effect, the workspace is currently unusable and a threat to the live frontend.
Updated by Christian Rieke almost 10 years ago
- Assignee deleted (
Ernesto Baschny) - Target version deleted (
next-patchlevel)
Quick update:
Checked with a Bootsrap package (6.2.3) out of the box: Following the procedure outlined in the original bug report I now find 4 images in the frontend (instead of the 1 that should be visible). After publication of the draft workspace, all 4 images still remain. But still only 1 image is accessible in the backend.
Updated by
Updated by Christian Rieke about 9 years ago
To my knowledge this issue has already been resolved with one of the last bugfixes (6.2.5?).
Updated by Riccardo De Contardi almost 9 years ago
this is the test I've done with TYPO3 6.2.12:
enviroment:
1.create a user group: name:editors; Edit Live (Online):yes
2.create a new user: editor ,assign to group: editors; Edit Live (Online):yes
3. create a new workspace:
name: "Draft before publishing"
owners:none
members: editor
DB Mounts:from Home page
all the other fields are as default.
log in as editor
1. LIVE workspace
1.1. create new CE, text with image; add image1.png, save
2. switch to "Draft before publishing" workspace
3. edit the CE with image1.png; add image2.png and delete image1.png, NOT SAVE the element
3.1 open new tab > go to Frontend > image shown: image1.png
4.1 save the CE > go to Frontend > image shown: image2.png
5. open another browser > go to Frontend > image shown: image1.png
so as far, the behavior seems correct. I will test in 7.x too
Updated by Riccardo De Contardi over 8 years ago
- Status changed from New to Closed
I am not able to reproduce this issue with both TYPO3 6.2.15 and 7.5-dev (latest master), so I close this for now.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.