Bug #38417
closed
Duplicate tt_content translation records in the database
0%
Description
I just spent some hours debugging a TYPO3 installation we are maintaining. We changed some localized records in the backend but the changes were not shown in the frontend. I thought it was a caching problem but after some time of researching I found out there ware some duplicate localization records in the database, see Image 1.
Query used:SELECT pid, uid, l18n_parent, sys_language_uid, deleted, hidden, tstamp, crdate, cruser_id FROM tt_content WHERE l18n_parent = 14473 AND deleted = 0 ORDER BY sys_language_uid ASC, tstamp ASC
I am pretty sure this should never happen... That duplicate entries made it nearly impossible to debug because only one record per language was shown in the backend. Unfortunately, this record was not the record shown in the frontend, so I modified a record which was not shown in the frontend but in the backend. I had no chance to edit the second record in the backend, it was not even visible in the list-view (which, of course, is filtering by one record per language).
I wrote a quick and dirty PHP script to check some other installations and a lot of setups had duplicate records. I attached that script so you can check out your installations, too.
All installations are on 4.5.17 right now but a lot of upgrading was done over the years. The site I found that mistake was installed on 4.4.
Files
Updated by Philipp Gampe over 12 years ago
Can you try to find out if this still happens or if this are leftovers from an older bug?
Updated by Dennis Schubert over 12 years ago
The last duplicate stuff was created two weeks ago (if the timestamp is correct, what I presume), so this is not an old bug. :-(
Updated by Patrick Hafner over 12 years ago
Got the same problem in TYPO3 4.5.14 and tt_news 3.0.1
Updated by Dennis Schubert over 12 years ago
It's been a while so I will kindly push that ticket... Any ideas?
Updated by Dennis Schubert almost 12 years ago
Fun. Still getting duplicates on new records. Is it really just us?
What I realized: TYPO3 sometimes creates duplicate records when duplicating a page in the backend with the ajaxy page tree. The request seems to get canceled after some seconds and if your pages are huge, you get duplicate records! Different UIDs, same PIDs, same i18n_parents.
Updated by Philipp Gampe almost 12 years ago
That could well be, if the server responds too late to the request. You better do not use the page tree for large copy operations.
I am not much into the translation part of the core, so I can not say much. Maybe you could check whether this happens on high load times.
Updated by Dmitry Dulepov almost 12 years ago
I think I saw this but the reason was in either wrong character set of the database or something like that. In my case it did not happen in the normal set up. It was definitely a problem of the installation.
I do not imply that there is no problem. Just adding the information I have.
Updated by Mathias Schreiber almost 10 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
- Is Regression set to No
Did the error clear up?
Updated by Dennis Schubert almost 10 years ago
Nope. We still have duplicated translations occasionally on 4.5 installations and we need to manually remove them.
Updated by Mathias Schreiber almost 10 years ago
could this be tracked down to requests that stop prematurely?
Updated by Dennis Schubert almost 10 years ago
Not that I'm aware of. All AJAX requests finished in our tests (verified via the browsers Developer Tools).
Updated by Alexander Opitz over 9 years ago
As 4.5 will only get security fixes, does this issue exists in a 6.2 release of TYPO3 CMS?
Updated by Alexander Opitz about 9 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Mathias Schreiber)
No feedback within the last 90 days => closing this issue.
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.