Bug #21873
closed
alternative page language will be deleted in new workspaces after publishing
Added by Marcel Fiedrich over 14 years ago.
Updated almost 14 years ago.
Description
if I published an alternative page language that I have created in a new created workspace the record will be deleted.
(issue imported from #M13075)
Files
I've tested this issue again in a fresh installed TYPO3 Backend (Ver. 4.3.1).
I've created a new alternative page language in the Draft system-workspace and tried to swap the versions.
after i have clicked the swap-button the page is deleted.
I have fixed the bug.
In /t3lib/class.t3lib_tcemain.php on line 4730 the "transOrigPointerField" will be kept.
That's ok if it's the l18n_parent field, but for the "pages_language_overlay" table is it the "pid"-Field.
If you publish/swap a page overlay record, the pid field will always change to -1.
so I have changed the if-construct from:
if ($TCA[$table]['ctrl']['transOrigPointerField'])
to:
if ($TCA[$table]['ctrl']['transOrigPointerField'] && $table != 'pages_language_overlay')
or to:
if ($TCA[$table]['ctrl']['transOrigPointerField']!='pid')
I think both ways should work.
I can confirm this. It's 100% reproducable here and is giving my editors a hard time.
Confirmed that the problem exists with 4.3.2
Uploaded patch 13075-versionswap-alternativepage.patch fixing the issue against the TYPO3_4-3 branch.
I have the same Issue on 4.3.3 dev!
This should be a Major issue since content gets lost!
I'm also seeing this issue on 4.3.2. Upon publishing changes to the page overlay pid field in pages_language_overlay changes to -1 instead of the correct page id and thus content vanishes from view.
The patch 13075-versionswap-alternativepage.patch solved the issue on 4.3.2.
The pathc worked for me on 4.3.2. Thank you very much.
But:
on 4.3.3 this problem occurs again. I think the patch does not work there.
this is a duplicate of #13818 which is already pending in the core-list and waiting for review
Confirmed that the patch 13075-versionswap-alternativepage.patch still successfully fixes the issue against Typo3 4.3.3
Confirming the patch to also work with 4.3.0.
This issue should probably be labeled as major.
Hi guys,
please have a look at the thread for #13818 in Core List!
Tolleiv already posted his patch there. But it will not be integrated if not anyone gives his +1 on reading and testing.
Also available in: Atom
PDF