genericsetup

How do I prevent values of custom registry entries to be overwritten on reinstall of my package?

由 别等时光非礼了梦想. 提交于 2019-12-11 03:49:09
问题 My package introduces registry entries. Changes by site administrator should not be overwritten on reinstall of the package. Many ways to Rome. I chose ftw.upgrade. I like the declarative way of the upgrade step syntax. Its possible to use an upgrade directory for generic setup xml-Files like propertiestool.xml. No need to define handler python code. The upgrade works well. The admin can upgrade from control panel and in my case the new property is added. Insomma: For a new property just

Is there a good reference list for the names of the genericsetup import steps

由 隐身守侯 提交于 2019-12-10 05:20:15
问题 Is there a comprehensive reference list of the generic setup import step names? The names of generic setup import steps don't always match the names of their corresponding xml files for example 'types.xml' has an import step called 'typeinfo'. In the absence of a list, I would be satisfied with a simple approach to finding out the name of the import step. For example the import step name for plone.app.registry which is managed by the 'registry.xml' file is not obvious, I tried to refer to it

Is there a good reference list for the names of the genericsetup import steps

由 安稳与你 提交于 2019-12-05 10:02:12
Is there a comprehensive reference list of the generic setup import step names? The names of generic setup import steps don't always match the names of their corresponding xml files for example 'types.xml' has an import step called 'typeinfo'. In the absence of a list, I would be satisfied with a simple approach to finding out the name of the import step. For example the import step name for plone.app.registry which is managed by the 'registry.xml' file is not obvious, I tried to refer to it as 'registry' but this fails, see code below: from Products.CMFCore.utils import getToolByName PROFILE
订阅 genericsetup