|
not only module wide, but also site wide i18nBasename would be nice. It would be also nice if such value exists, if it can be used as a fallback for properties not found in the message bundle that was specified.
Useful for extra stk templates added by other modules (e.g. newsletter). Currently, either messages for such template (title and description) have to either be added to the stk template bundle, or the other messages used in the template page (extras.newLabel, basename.newLabel, etc. ) have to be copied to the module specific message bundle used by the template.
|
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.
|