Actions
Bug #14920
closed
Irritating field name "l18n_parent"
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2005-08-11
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
3.8.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
If a new module including new tables with i18n support is created, these tables
get a new field "l18n_parent" which determines the parental relationship of a translated field to the original field.
However, this field is named wrong, it should either be "l10n_parent" ("localisation parent") or "i18n_parent" ("internationalisation parent") but not a mixture of both ("l18n_parent"). I first thought the "l" was a big "I" which looks equally with sans-serif fonts and wondered why my SQL didn't work...
(issue imported from #M1368)
Updated by Martin Kutschker over 19 years ago
It's too late now to change it and it's not the only spelling problem in the API.
Actions