New contrib: Locations (workflow event)

Author Message

Łukasz Serwatka

Sunday 18 September 2005 1:25:15 am

With this workflow event you can automate publishing process. You can publish article/image/file or other object in multiple locations. Additional object locations you can define in configuration INI file.

Check it here:
http://ez.no/community/contribs/workflow/locations_workflow_event

Enjoy!

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Xavier Dutoit

Sunday 18 September 2005 3:38:22 am

Hi Lukasz,

Just to fully understood, what's the benefit of using the workflow over SetPlacementNodeIDArray[] into the edit form ?

Thanks in advance,

X+

http://www.sydesy.com

Łukasz Serwatka

Sunday 18 September 2005 4:12:03 am

Hi Xavier,

Maintenance, better is keep data about new locations for objects created from custom classes in INI file (especially when I need use that functionality in several places in website), than adding more and more hidden fields in templates. This is just alternative. You decide what you will use.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Claudia Kosny

Monday 27 November 2006 4:42:41 am

Hi Lukasz

I can't get your extension to work on EZ 3.8.3. If I print the node assignment (directly after the line where it is stored) I get this:

eznodeassignment Object
(
    [PersistentDataDirty] => 
    [ID] => 456
    [RemoteID] => 0
    [ParentRemoteID] => 
    [ContentobjectID] => 245
    [ContentObjectVersion] => 23
    [ParentNode] => 83
    [SortField] => 2
    [SortOrder] => 0
    [Main] => 0
    [FromNodeID] => 0
    [TempNode] => 
    [Name] => 
    [OpCode] => 3
)

Unfortunately the content object does not appear under the additional node assignment and I have no idea what to do.
The trigger is set to content before publish. The designated parentnode for the new assignment is a container. I don't get any debug or error messages. I have emptied the cache before and after editing an object to make sure it is not a caching problem.

I have also tried to trigger this event on after publish and then publish the object again within this event but the result is the same.

Could you give me any hints on how to troubleshoot this?

EDIT:
Solved, the problem was a) that I need to use $parameters['version'] instead of $object->attribute( 'current_version' ) as the current version is the published version instead of the version that is in the process of being published
and b) I had to update the function publishNode in \kernel\content\ezcontentoperationcollection.php to the 3.8.4 version.

Not sure why, but it works fine now.
/EDIT

Thanks

Claudia

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.