Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.5.10
-
Fix Version/s: None
-
Component/s: core
-
Labels:None
Description
When create a new LocaleMgr object and specifying a path to a locales.d folder it has no effect.
The check for prefixpath prevents to scan for the locales.d folder:
Instead using the instance method loadConfigPath(<path to locales.d>) works.