[Erp5-dev] Using some global actions for actions common to all portal types

[Jérome Perrin]

Hi

Some actions like History, Medatada or Print PDF are defined on all
portal types. The idea is to replace those actions defined everywhere by
global actions.
I added those global actions in r15631 and r15632, so now we need to
remove actions from existing portal types, otherwise they are displayed
twice.

I will myself remove actions from the most common business templates,
but if you want to update your business templates, you can use the
attached script.

Call this script on the context of the business template, it will remove
actions from portal_types and in the business template itself, so that
you just have to export it again.

J?rome
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: BusinessTemplate_removeOldStyleActions.py
URL: <http://mail.tiolive.com/pipermail/erp5-dev/attachments/20070813/c2fe53ae/attachment.asc>

[Jean-Paul Smets]

Quick note:
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).
JPS.

Post by Jérome Perrin
Hi
Some actions like History, Medatada or Print PDF are defined on all
portal types. The idea is to replace those actions defined everywhere
by global actions.
I added those global actions in r15631 and r15632, so now we need to
remove actions from existing portal types, otherwise they are
displayed twice.
I will myself remove actions from the most common business templates,
but if you want to update your business templates, you can use the
attached script.
Call this script on the context of the business template, it will remove
actions from portal_types and in the business template itself, so that
you just have to export it again.
J?rome
------------------------------------------------------------------------
_______________________________________________
Erp5-dev mailing list
Erp5-dev at erp5.org
http://erp5.org/mailman/listinfo/erp5-dev

[Jérome Perrin]

Post by Jean-Paul Smets
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).

Actions from portal types will always be displayed before global
actions, but they will not replace global action.
This means that if you define a custom print (or search, export ...)
action for a given portal type, your portal type action will be the one
selected by default.

J?rome

[Yoshinori Okuji]

Post by Jérome Perrin

Post by Jean-Paul Smets
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).

Actions from portal types will always be displayed before global
actions, but they will not replace global action.
This means that if you define a custom print (or search, export ...)
action for a given portal type, your portal type action will be the one
selected by default.

Actually, I don't like the idea of having completely the same actions
everywhere. When I looked at a ODS export global action, it was even added to
portal_templates, and it was simply annoying for me. So we need to be a bit
more careful about where we want to enable global actions.

YO

[Jean-Paul Smets]

Post by Yoshinori Okuji

Post by Jérome Perrin

Post by Jean-Paul Smets
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).

Actions from portal types will always be displayed before global
actions, but they will not replace global action.
This means that if you define a custom print (or search, export ...)
action for a given portal type, your portal type action will be the one
selected by default.

Actually, I don't like the idea of having completely the same actions
everywhere. When I looked at a ODS export global action, it was even added to
portal_templates, and it was simply annoying for me. So we need to be a bit
more careful about where we want to enable global actions.

What is the problem of having ODS export action for BT ?

JPS.

Post by Yoshinori Okuji
YO

[Jérome Perrin]

Post by Jérome Perrin

Post by Jean-Paul Smets
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).

Actions from portal types will always be displayed before global
actions, but they will not replace global action.

This is actually too anoying, I will add a script that filter out
duplicate actions (ie. actions with the same ID from the same category).
This way you won't have duplicate actions, and it will be possible to
replace a global action.

J?rome

[Jérome Perrin]

Post by Jérome Perrin
I will add a script that filter out
duplicate actions (ie. actions with the same ID from the same category).
This way you won't have duplicate actions, and it will be possible to
replace a global action.

This is done in http://svn.erp5.org?rev=15737&view=rev

J?rome

[Mikolaj Antoszkiewicz]

Post by Jérome Perrin

Post by Jean-Paul Smets
about Print "action", is it still possible to override the default
print action ?
(it OK for me to keep the default one in second).

Actions from portal types will always be displayed before global
actions, but they will not replace global action.
This means that if you define a custom print (or search, export ...)
action for a given portal type, your portal type action will be the one
selected by default.

Should it be enough if I just add the 'print' action to the portal type, or do
I have to configure something for the form to execute my action not the
global one?
I've added 'print' action (as object_print category) to Sale Invoice
Transaction portal type, but clicking the printer icon still executes
standard Base_print ....

Mikolaj

[Jérome Perrin]

Post by Mikolaj Antoszkiewicz
Should it be enough if I just add the 'print' action to the portal type, or do
I have to configure something for the form to execute my action not the
global one?
I've added 'print' action (as object_print category) to Sale Invoice
Transaction portal type, but clicking the printer icon still executes
standard Base_print ....

Hi,
This was a bug, fixed by this commit:
http://svn.erp5.org?rev=16233&view=rev

J?rome