Creating language folder(s) on installation. #215
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
small potatoes, but should init_pma be init_pam? |
iham
added a commit
that referenced
this pull request
Mar 8, 2016
Creating language folder(s) on installation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Having predefined languages (in a registry.xml or manual inside the portal) now creates the folders (LRF and LIF) on the fly when installing plone.app.multilingual.
This is extremely useful when using GenericSetup to install plone.app.multilingual as a dependency and/or having language settings done upfront.
It wasn't useful to create an additional profile for that as the folder creation routine doesn't destroy or overwrite any existing content.
This fixes #214