Hi there, George Lefter wrote: > At the moment, if an action specifies a position (the order attribute) > and the others dont, then the ordering is not correct. (I tried to > create a new action "Content" with order=0, but it was added at the end).
That's not normal. The default action order should 0. It's an actual
bug. I suppose it's a regression.
> What is the right way to do this? Should we assign default values for
> actions that do not specify the order attribute?
yep => order=0
> Does it help if the default values are in steps of 10 (e.g 0, 10, 20, 30) ?
You only need one default value when not specified. For the order of
"default" actions. (i.e : view, modify, history, relations, workflow,
etc...). Yes steps of 10 are a good move.
> Or maybe use constraints like "first", "last", "after action-id" and
> "before action-id"?
nope I wouldn't go for that.
J.
--
Julien Anguenot | Nuxeo R&D (Paris, France)
Open Source ECM - http://www.nuxeo.com
Nuxeo 5 : http://www.nuxeo.org
Mobile: +33 (0) 6 72 57 57 66
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm
