Issue Bug Closed

#28223Localization of a constant string is empty

Xavier Perseguers 07/15/11, 09:26 updated 06/01/13, 14:45

Description

When using a constant string (e.g., “CSS Styled Content”) instead of a localization key (e.g., “LLL:EXT:some_ext/locallang.xml:key”), the constant string should be returned. At the moment, the localization fails to find the entry in the non-existing localization file and returns an empty string instead.

This is visible when editing all configuration of a template, the “include static (from extension)” list is empty instead of showing all available statit templates provided by the various extensions.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.