You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thats my scenario:
I have a package holding GenericSetup configs like registry.xml including language-settings (which languages are used, default language and negotiation for example). Also i want to install dependencies. PAM and others in this case.
So installing my package does the settings correct and also installs PAM. So far so good.
But the LRF and LIF folders are not created. Therefore i had to go to Plone's control panel -> language settings and hit "save" without any changes done to trigger the creation process of PAM.
I found out that i can trigger that after my package installation by using plone.app.multilingual.browser.setup.py's code
inside my setuphandler (using GS 1.8.2+ i can use post_handler on my profile's registry)
I don't think this should be in my package as this seems pretty default to me, to get the language folders and all other stuff set, when having my configs and installing PAM, when building a new portal.
My first thought was: why doesn't PAM run this on installation as it doesn't override/replace any existing content or delete stuff during that process.
Thats my scenario:
I have a package holding GenericSetup configs like registry.xml including language-settings (which languages are used, default language and negotiation for example). Also i want to install dependencies. PAM and others in this case.
So installing my package does the settings correct and also installs PAM. So far so good.
But the LRF and LIF folders are not created. Therefore i had to go to Plone's control panel -> language settings and hit "save" without any changes done to trigger the creation process of PAM.
I found out that i can trigger that after my package installation by using plone.app.multilingual.browser.setup.py's code
inside my setuphandler (using GS 1.8.2+ i can use post_handler on my profile's registry)
I don't think this should be in my package as this seems pretty default to me, to get the language folders and all other stuff set, when having my configs and installing PAM, when building a new portal.
My first thought was: why doesn't PAM run this on installation as it doesn't override/replace any existing content or delete stuff during that process.
plone.app.multilingual
configure.zcml
setuphanders.py
The other idea by @pbauer: add a second profile depending on the default profile that i can trigger as a dependency in my package then.
configure.zcml
metadata.xml
setuphanders.py
my metadata.xml would look like that then:
Any considerations?
Better ideas?
The text was updated successfully, but these errors were encountered: