3.9 section assignment on object modification

Next topic

Author	Message
Kristof Coomans	Sunday 20 August 2006 4:15:00 am I just took a quick look at the eZ publish 3.9 code which allows the modification of the section of an object in the content/edit view. When the section is changed in the content/edit view, a session variable ShouldNotUpdateSectionID is set to skip some code for section inheritance in the content/publish operation. I wonder if this will work if a pre-publish workflow with an approve event is used, or any other event which defers to the cron, because that will be another session? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Kristof Coomans	Sunday 20 August 2006 4:37:18 am I also noticed that the policy for the section module is not respected. Maybe it's a good idea to add limitation parameters (content class, subtree, current section, new section) to a policy for section assignment, so this feature can be used safely by end users (like editors) too. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Valentin Doroschuk	Tuesday 22 August 2006 8:15:55 am Hi Kristof,, Thanks a lot for your comments... Fixed in 3.9.0alpha1 (trunk rev. 16689). Now when an object is created section_id will be set to '0', when publishing eZContentOperationCollection::updateSectionID() will be called and sectionID will be updated. what about limitations... maybe in subrealeses....

Author

Message

Sunday 20 August 2006 4:15:00 am

I just took a quick look at the eZ publish 3.9 code which allows the modification of the section of an object in the content/edit view.

When the section is changed in the content/edit view, a session variable ShouldNotUpdateSectionID is set to skip some code for section inheritance in the content/publish operation. I wonder if this will work if a pre-publish workflow with an approve event is used, or any other event which defers to the cron, because that will be another session?

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Kristof Coomans

Sunday 20 August 2006 4:37:18 am

I also noticed that the policy for the section module is not respected.

Maybe it's a good idea to add limitation parameters (content class, subtree, current section, new section) to a policy for section assignment, so this feature can be used safely by end users (like editors) too.

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Valentin Doroschuk

Tuesday 22 August 2006 8:15:55 am

Hi Kristof,,
Thanks a lot for your comments...

Fixed in
3.9.0alpha1 (trunk rev. 16689).

Now when an object is created section_id will be set to '0',
when publishing eZContentOperationCollection::updateSectionID() will be called
and sectionID will be updated.

what about limitations...
maybe in subrealeses....