Upgrade plans for EzPublish v3 -> 3.1 etc. Available and in the roadmap??

Author Message

Jørgen Skogstad

Saturday 26 April 2003 11:53:21 am

Just curious about this since I would not like to be stranded on a given version .. and then have to redo _alot_ of work upgrading to a newer version.

What are the plans to provide an upgrade path to a newer version of EzPublish? This should be provided and part of the release plan of Ez, but I have not seen any statements about this.

Anyone that knows anything .. and/or have information to share??!

Kindest,
Jørgen SKogstad

Ekkehard Dörre

Sunday 27 April 2003 3:29:00 am

You read the information on
http://ez.no/developer/news/ez_publish_31_release_plan ?

Greetings,
ekke

http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing

Jørgen Skogstad

Wednesday 30 April 2003 2:16:09 pm

Yep .. there is nothing there about that .. what I was wondering was if upgrade database scripts / ++ was available and the _supported_ way of updating a server install to a new version.

.. this should be an integral part of EzPublish. It might very well be there, but I have not seen anything that commits Ez do do release planning in this way. I just want to know if people are "stranded" on the install they have .. or have a seamless upgrade path as long as they follow the track of the releases.

Kindest,
Jørgen

Paul Borgermans

Friday 02 May 2003 12:45:18 am

Don't worry,

You only get "stranded" when you modify the existing php scripts and leave them the currrent modules.

Database upgrades have been there since the beta series.

Make sure all your settings are in the override dirs and use a siteacces that is not called user/demo/admin/standard.

Then, upgrading is just a matter of database upgrades (if any) and the copying of files + modfixing + ownership (webserver userid) and clearing the cache. Stop the apache server daemons to be sure no database corruption can occur during the upgrades. See also the user contributed docs if you are upgrading from the svn repositories (and keep track of changes in the database upgrade scripts).

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

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 04:55:46
Script start
Timing: Jan 18 2025 04:55:46
Module start 'layout'
Timing: Jan 18 2025 04:55:46
Module start 'content'
Timing: Jan 18 2025 04:55:47
Module end 'content'
Timing: Jan 18 2025 04:55:47
Script end

Main resources:

Total runtime0.7812 sec
Peak memory usage4,096.0000 KB
Database Queries62

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0062 589.6094152.6563
Module start 'layout' 0.00620.0036 742.265639.5234
Module start 'content' 0.00980.7698 781.7891602.7656
Module end 'content' 0.77960.0016 1,384.554712.0781
Script end 0.7811  1,396.6328 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00310.4016160.0002
Check MTime0.00140.1786160.0001
Mysql Total
Database connection0.00070.090410.0007
Mysqli_queries0.720192.1758620.0116
Looping result0.00070.0940600.0000
Template Total0.746695.620.3733
Template load0.00200.250020.0010
Template processing0.744695.316320.3723
Template load and register function0.00020.020010.0002
states
state_id_array0.00220.275710.0022
state_identifier_array0.00110.146320.0006
Override
Cache load0.00150.1929290.0001
Sytem overhead
Fetch class attribute can translate value0.00070.087230.0002
Fetch class attribute name0.00180.225370.0003
XML
Image XML parsing0.00370.476830.0012
class_abstraction
Instantiating content class attribute0.00000.001880.0000
General
dbfile0.00390.4972290.0001
String conversion0.00000.001140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
4content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
4content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
7content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
4content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 21
 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs