Bug #25396
closed
Database inconsistence between sys_language_uid and language-id value in "l10n_diffsource"
Added by Gabriel Kaufmann / Typoworx NewMedia over 13 years ago.
Updated about 10 years ago.
Description
I noticed that there seems to be an inconsistency between the database fields "sys_language_uid" and the value given in "l10n_diffsource".
I think to remember of this problem in default database records (like pages, tt_content) too while selecting records using Typoscript CONTENT in TemplaVoila environment (not shure).
Is there anyone who can confirm this bug?
The current issue has been noticed while programming on a custom FE-Plugin started using "kickstarter" Extension (Database Layout). I made some example records with multi-language translations and tried to program a proper FE-Listing for them.
While that I noticed that a WHERE-Clause for MySQL does not always return the correct records selected by "sys_language_uid". The mistake is that there seem to be different values between the field "sys_language_uid" and the serialized field "l10n_diffsource" also containing a sys_language_uid value.
The only way
(issue imported from #M18039)
What's the reason to make this issue private? Doesn't look like it's a security issue..
I wasn't shure if the error report is basing on a true error. While entering this issue I decided to have a close look to it first. I thought the "private flag" gives me the ability to check this report in later (my mistake sorry).
Maybe the best will be to make it public and see what others think about the report.
Fine, I made it public now. I think you can't do that yourself - so please only use it for security issues.
If you're unsure whether it's a real bug, you can consult the mailing lists first.
Regards
Steffen
- Status changed from New to Needs Feedback
- Target version deleted (
0)
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?
- Status changed from Needs Feedback to Closed
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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by