setting priority on publish

Friday 29 September 2006 2:11:46 pm

Hallo Marko

I think I would try to it this way:
Add an integer attribute to each contentclass which will allow your editors to set the priority.
Create an extension that will grab an object by their id and fetch the main node beloging to this objct. Fetch the value of the integer attribute holding your priority and set the priority of the main node to this value using setAttribute.
Create a workflow that will execute this extension right after publishing an object.

The only problem I see with this approach is that the object is already published before you change the node priority whereas it would be nice to it in one step.

(Actually I would not use an additional attribute but insert a custom input field in the edit template and then just hack the content/edit.php to set the node priority to whatever was posted as this is a matter of 15 min work whereas I still have not managed to have a look at workflows and thus tend to avoid them. But doing it without changing kernel files is certainly more flexible and less error prone)

Greetings from Luxembourg

Claudia

Saturday 30 September 2006 8:32:52 am

Ah this looks very interesting. Thanks for the tip.

Claudia

Friday 06 October 2006 8:51:49 am

Hello Marko

Yes you are right, this does not work for different locations. But wouldn't that be a problem no matter how you do it? After all you edit an object and although the objects knows its node assignments there is no way to know whether the content of your (hypothetical) priority field is meant for one or the other location. Or is that possible?

Of course you could always fetch a list of all the node assignments together with an input field for the new priority for each assignment and then process this data. I hope this is not to complicated as I need to do something similar within the next couple of days...

Greetings from Luxembourg

Claudia