It seems normal to me - if the default order=0, and I add another action with
order=0,
how can it know that I want it first?
I forgot to mention that I added the new action in another component - in GEIDE.
Probably we should define explicit order values for actions in Nuxeo, in steps
of 10.
After that, if needed, GEIDE can re-define the order.
Julien Anguenot wrote:
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.
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
