Actions
Bug #99298
closed
requireApprovedLocalizations should allow localizations with no approved attribute
Start date:
2022-06-06
Due date:
2022-06-06
% Done:
0%
Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Followup to #97729
If `$GLOBALS['TYPO3_CONF_VARS']['SYS']['lang']['requireApprovedLocalizations']` is not set to false, only xlf translations are respected if an approved attribute is set to yes. however if no approved is defined, those should be taken into account as well!
Updated by Georg Ringer about 2 years ago
- Due date set to 2022-06-06
- Start date changed from 2022-12-07 to 2022-06-06
- Follows Feature #97729: Support attribute approved in xlf added
Updated by Oliver Schmidt about 2 years ago
Thank you. Great idea. Had an issue based on that, was not that easy to find out that the new feature was my problem.
Updated by Benni Mack almost 2 years ago
- Target version changed from 12.2 to 12.3
Updated by Georg Ringer almost 2 years ago
- Related to Bug #99265: Text in backend modules are not localized to (e.g.) german in TYPO3 12 added
Actions