Friday 04 March 2011 7:13:41 am - 5 replies

Introduction

 

This is a checklist of actions for an update of an eZ Publish website. Comments/contributions are welcome.

» Read full blog post

Author Message

Greg McAvoy-Jensen

Friday 04 March 2011 8:25:47 am

Thanks, Gaetano--especially for the tip on how to "warm up" the caches!

Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog

Geoff Bentley

Friday 04 March 2011 5:41:36 pm

Great checklist. Hands up who wishes that making an update were simpler? Of course, a lot can be scripted, BUT, I would request that some serious thought is put into making updating the following easier:

  1. roles & policies
  2. workflows

     

  3. sections

     

  4. object states definitions

If there was an option for packaging up content classes and any associated roles & policies, that would make life so much easier!

Damien Pobel

Monday 07 March 2011 3:26:49 am

Interesting checklist. For "[optional] put the public website offline" part, I wrote an article almost 3 years ago with a way to do that in the Apache configuration, there's also alternatives ways of doing the same things in the comments.

Cheers

Damien
Planet eZ Publish.fr : http://www.planet-ezpublish.fr
Certification : http://auth.ez.no/certification/verify/372448
Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish

bisk

Saturday 12 March 2011 1:01:58 am

Followed this checklist yesterday, everything went smooth without any hickups. Had a backup ready just in case, but not needed. Thanks for the writeup, was helpfull.

-------------------------------
http://www.kookfijn.nl & http://www.magento.be

Marko Žmak

Monday 14 March 2011 3:11:46 pm

Nice checklist... Here are two little details also worth mentioning:

  • regenerate static cache before putting the site online (bin/php/makestaticcache.php)
  • test the upgraded site on the server before putting it online :)

--
Nothing is impossible. Not if you can imagine it!

Hubert Farnsworth

You must be logged in to post messages in this topic!

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 30 2025 00:14:45
Script start
Timing: Jan 30 2025 00:14:45
Module start 'layout'
Timing: Jan 30 2025 00:14:45
Module start 'content'
Timing: Jan 30 2025 00:14:46
Module end 'content'
Timing: Jan 30 2025 00:14:46
Script end

Main resources:

Total runtime0.0135 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.0044 588.3906151.2422
Module start 'layout' 0.00440.0023 739.632836.7188
Module start 'content' 0.00670.0054 776.351698.9063
Module end 'content' 0.01210.0014 875.257837.9766
Script end 0.0135  913.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002518.6527140.0002
Check MTime0.00139.9180140.0001
Mysql Total
Database connection0.00054.039010.0005
Mysqli_queries0.002215.957130.0007
Looping result0.00000.081010.0000
Template Total0.00118.110.0011
Template load0.00096.505710.0009
Template processing0.00021.528310.0002
Override
Cache load0.00064.732710.0006
General
dbfile0.001914.386680.0002
String conversion0.00000.049340.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