Bug #16847
closedDeleting localized content elements fails
0%
Description
Assuming that you have a content element (tt_content) that is available in two languages, such as :
+ Hello World - Localization : Default (English)
\--- Bonjour le monde - Localization : French
When you hit the "Delete record" button for the default language element, the two of them disappear from the BackEnd, but only the default language element's "deleted" flag in tt_content is set to 1. So that the localized one is still active, visible on the FrontEnd, but not accessible anymore in the BackEnd. It should have been deleted...
The following SQL script allows us to find elements that have not been deleted when their "father" has been.
SELECT
t1.uid as 1_uid,
t1.deleted as 1_deleted,
t1.pid as 1_pid,
t1.sys_language_uid as 1_language,
t2.uid as 2_uid,
t2.deleted as 2_deleted,
t2.pid as 2_pid,
t2.sys_language_uid as 2_language
FROM tt_content t1, tt_content t2
WHERE
t1.deleted=1
AND t2.deleted=0
AND (
t1.uid = t2.l18n_parent
OR t2.uid = t1.l18n_parent
)
ORDER BY t1.pid ASC;
(issue imported from #M4762)
Updated by Tolleiv Nietsch about 15 years ago
I've just sent a patch to the dev-list (it resolved a couple of related issues as well) - I'd be glad to get some feedback
Updated by Tolleiv Nietsch about 15 years ago
that a duplicate of #14408 which was fixed and comitted yesterday - maybe someone could close it thx