[Erp5-dev] New BT installation option proposal

[Mikolaj Antoszkiewicz]

Hello Everybody!

Right now when installing a BT, there are two 'after-install' options to
choose from: update_catalog and update_translation
When there are any catalog entries the update_catalog options is 'on'
by default.

I was thinking about 'update_security' option. It would force
updateSecuritySettings on all portal_types and workflows.
When there are any new Role Definitions installed that option could also
be by default set to 'on'.
Without it, just like with catalog changes, the site might be
non-functional.


Mikolaj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3229 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.tiolive.com/pipermail/erp5-dev/attachments/20080606/d43bed37/attachment.bin>

[Jérome Perrin]

Post by Mikolaj Antoszkiewicz
Hello Everybody!
Right now when installing a BT, there are two 'after-install' options to
choose from: update_catalog and update_translation
When there are any catalog entries the update_catalog options is 'on'
by default.
I was thinking about 'update_security' option. It would force
updateSecuritySettings on all portal_types and workflows.
When there are any new Role Definitions installed that option could also
be by default set to 'on'.
Without it, just like with catalog changes, the site might be
non-functional.

Hello,

For me this is a good idea.

J?rome

[Romain Courteaud]

Post by Jérome Perrin

Post by Mikolaj Antoszkiewicz
Hello Everybody!
Right now when installing a BT, there are two 'after-install' options to
choose from: update_catalog and update_translation
When there are any catalog entries the update_catalog options is 'on'
by default.
I was thinking about 'update_security' option. It would force
updateSecuritySettings on all portal_types and workflows.
When there are any new Role Definitions installed that option could also
be by default set to 'on'.
Without it, just like with catalog changes, the site might be
non-functional.

Hello,
For me this is a good idea.

Hello,

I have a different point of view than yours.

On the one hand, update_catalog and update_translation options don't
modify the data in the ZODB, but only their index in the catalog.

On the other hands, 'update_security' option will lead to an huge
modification in the data. In such case, I think it is better that the
site's administrator launch a script itself if he really want to do
such data migrations (update local roles, permissions, ...).

Regards,
Romain

[Łukasz Nowak]

Hello,

Post by Jérome Perrin

Post by Jérome Perrin

Post by Mikolaj Antoszkiewicz
Hello Everybody!
Right now when installing a BT, there are two 'after-install' options to
choose from: update_catalog and update_translation
When there are any catalog entries the update_catalog options is 'on'
by default.
I was thinking about 'update_security' option. It would force
updateSecuritySettings on all portal_types and workflows.
When there are any new Role Definitions installed that option could also
be by default set to 'on'.
Without it, just like with catalog changes, the site might be
non-functional.

Hello,
For me this is a good idea.

Hello,
I have a different point of view than yours.
On the one hand, update_catalog and update_translation options don't
modify the data in the ZODB, but only their index in the catalog.
On the other hands, 'update_security' option will lead to an huge
modification in the data. In such case, I think it is better that the
site's administrator launch a script itself if he really want to do
such data migrations (update local roles, permissions, ...).

Is it acceptable to provide such set of scripts? Like this one attached?

Regards,
Luke
--
?ukasz Nowak R&D Ventis http://www.ventis.com.pl/
tel: [phone] fax: [phone]
``Use the Source, Luke...'' I am only craftsman.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: BusinessTemplate_updateRoleMapping.py
Type: text/x-python
Size: 782 bytes
Desc: not available
URL: <http://mail.tiolive.com/pipermail/erp5-dev/attachments/20080902/ddd886a1/attachment.py>