Object States Deployment on a live site

Author Message

Marco Caldari

Monday 07 September 2009 3:08:51 am

Hello,
Following the very interesting article by Nicolas Pastorino found here http://ez.no/developer/articles/ez_publish_knowledge_series_editorial_workflow_with_object_states I have set up an 'object state' workflow on a live website now I have 2 question that maybe someone on the forum has already faced to,

1. The website is live and we have right now some 15k articles that passed to 'bulk_edition' state as I set up the thing, so are not visible by the new anonimous user, it is not possible to maually assign the 'ready_to_live' state to each one of the 15k already published articles, is there a way to mass set 'ready_to_go_live' to all? Something like assign to all the children of some folder the right state?

2. Is it possible to flag with different icons the state of an article in the list view in the admin interface? This would be nice, infact as the admin goes in can see mixed 'ready_to_go_live' and 'bulk_edition' items and he has to view the single object to know its state, maybe this is only a template trick..

Any help is very appreciated,
thanks in advance,
Marco

Marco Caldari

Monday 07 September 2009 6:20:14 am

Here we go,
I answer to myself hoping that some ez guru could give more feedback on this topic or maybe add something in the new ez4.2 object states work,

1. To revert already published objects from 'bulk_editor' to 'ready_to_go', in my phpmyadmin:

UPDATE ezcobj_state_link
SET contentobject_state_id = REPLACE(contentobject_state_id, '3', '4')

with 4 corresponding to the 'ready_to_go_live' object state
It would be better to assign states from admin panel.. of course.

2. To notify in the Administrator admin panel which objects are waiting to be edited to pass to 'ready_to_go_live state' we added on children_list.tpl on /admin/templates/ the following:

{if eq($Nodes.object.state_id_array[3],3)}
<img src={'configure.png'|ezimage}  />
{/if}

With '3' that is the id for the bulk_editor state, this adds the icon on the side of the items in 'bulk_edition' state and the final editor can easily find them.

Thank You, for Your attention,
any further contrib is appreciated,
Marco

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

eZ debug

Timing: Jan 18 2025 18:33:50
Script start
Timing: Jan 18 2025 18:33:50
Module start 'layout'
Timing: Jan 18 2025 18:33:50
Module start 'content'
Timing: Jan 18 2025 18:33:50
Module end 'content'
Timing: Jan 18 2025 18:33:50
Script end

Main resources:

Total runtime0.0170 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0072 588.0313152.6406
Module start 'layout' 0.00720.0028 740.671939.4766
Module start 'content' 0.01000.0052 780.148489.3516
Module end 'content' 0.01530.0016 869.500030.3047
Script end 0.0169  899.8047 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.003520.3646140.0002
Check MTime0.00137.5562140.0001
Mysql Total
Database connection0.00084.979310.0008
Mysqli_queries0.002313.521530.0008
Looping result0.00000.099910.0000
Template Total0.00137.510.0013
Template load0.00074.283110.0007
Template processing0.00053.191510.0005
Override
Cache load0.00052.866610.0005
General
dbfile0.00032.039680.0000
String conversion0.00000.060540.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs