i tried to add a role to my plonesite (4.3.9) that is also displayed in the sharing tab and found out that this can't be done TTW.
either generic-setup (sharing.xml) or registering a persistent utility (what plone.app.workflow does for sharing.xml files) is needed.
so i tried to follow the path of least resistence (no package needed) and created a tarball for importing that consists of the following 2 files:
<?xml version="1.0"?> <rolemap> <roles> <role name="Notified"/> </roles> <permissions> <permission name="plone.app.blob: Add Blob" acquire="True"> <role name="Notified" /> </permission> </permissions> </rolemap>
<?xml version="1.0"?> <sharing xmlns:i18n="http://xml.zope.org/namespaces/i18n" i18n:domain="plone"> <role id="Notified" title="gets notified" permission="Plone Site Setup: Overview " i18n:attributes="title" /> </sharing>
however - this screwed up my whole site (of course there is a backup
all local roles (Editor, contributor, etc) where missing. all permissions have been reset (join form was visible, zope root manager user had no permission to request passwords for existing users, etc)
it seems the base-profile (never really understood this concepts and docs didn't help me much here) is missing for generic setup when importing the tarball and it does not apply these changes on top of the current settings but replaces all settings with the ones provided in this file.
in contrary - using these files in the the default or upgrade profile of an existing packages works fine.
where is the difference?
how can i make the tarball import work?
is there a way to fix my broken plone-site (by running a certain profile that restores the default roles and permissions of a plone site)?
is there a way to do a tarball import without