Plone product that allows you to define workflow policies that define content type to workflow mappings that can be applied in any sub-folder of your Plone site
I have noticed (probably again) in PR #37 that the GS profiles are confusing, and you easily make a mistake.
There is no default profile`.
The name of the profile taken when installing the product, is CMFPlacefulWorkflow.
This depends on a base profile which does most of the work.
The CMFPlacefulWorkflow says in the description that it "Includes a dependency on core Plone types." This is not the case (anymore). It only has a small rolemap.xml and defines a few actual policies.
Plus an uninstall profile, which is of course fine.
This is confusing, especially when writing upgrade steps: is the upgrade step for CMFPlacefulWorkflow or for base or for both?
Maybe we can merge CMFPlacefulWorkflow and base and call the result default? That would be ideal, and what people expect.
Downsides:
It might do too much for people in plain CMF or Zope. But we already import from CMFPlone. Not much, and might become plone.base. Anyway, it is probably not something we need to worry about. But please speak up if you do not agree.
It would be good if a third party add-on which wants to install our "main" profile, does not need to say: depend on A in Plone 5.2 and on B in Plone 6.
Maybe define CMFPlacefulWorkflow and default as duplicates of each other, both in 5.2 and 6.0. default will win then, at least in 5.2+.
Then come up with some way to switch from the old to the new in Plone 6 with a few upgrade steps. Theoretically:
Upgrade step for CMFPlacefulWorkflow which registers default as being installed in version 999.
Upgrade step for default from 999 to 1000 which unregisters CMFPlacefulWorkflow as being installed.
In the Modules control panel you need to upgrade twice then.
I have noticed (probably again) in PR #37 that the GS profiles are confusing, and you easily make a mistake.
default
profile`.CMFPlacefulWorkflow
.base
profile which does most of the work.CMFPlacefulWorkflow
says in the description that it "Includes a dependency on core Plone types." This is not the case (anymore). It only has a smallrolemap.xml
and defines a few actual policies.uninstall
profile, which is of course fine.This is confusing, especially when writing upgrade steps: is the upgrade step for
CMFPlacefulWorkflow
or forbase
or for both?Maybe we can merge
CMFPlacefulWorkflow
andbase
and call the resultdefault
? That would be ideal, and what people expect.Downsides:
CMFPlone
. Not much, and might becomeplone.base
. Anyway, it is probably not something we need to worry about. But please speak up if you do not agree.Maybe define
CMFPlacefulWorkflow
anddefault
as duplicates of each other, both in 5.2 and 6.0.default
will win then, at least in 5.2+.Then come up with some way to switch from the old to the new in Plone 6 with a few upgrade steps. Theoretically:
CMFPlacefulWorkflow
which registersdefault
as being installed in version 999.default
from 999 to 1000 which unregistersCMFPlacefulWorkflow
as being installed.In the Modules control panel you need to upgrade twice then.