Identifying older EZ Publish versions for upgrade purposes?

« 
Previous topic
|
General
|
Next topic
 »
Author Message

Paul Wilson

Wednesday 07 December 2005 2:48:23 am

Hi,

I'm trying to upgrade the database of an older EZ Publish site (somewhere around version 3.3 or 3.4), but I don't know what version it is. Because I can no longer run the site (PHP server upgrade), I can't view the site to find out what version it is to apply the database update files that are a part of the EZ Publish distribution.

Identifying newer versions of EZ Publish seems to be easy enough - its in the ezsite_data table of the database, but this does not exist on the database I've got.

Does anyone know how to identify the version number of a 3.3/3.4 site by looking at site or database content?

Thanks

Björn Dieding@xrow.de

Wednesday 07 December 2005 4:24:07 am

you have 2 options both may return the more or less correct version

look into the file lib/version.php

or

look into the table ezsite_data there is the version string saved there that gets applied each time you run update scripts

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Mark Marsiglio

Wednesday 07 December 2005 4:27:27 am

It is a bit of trial and error, but you could look at the upgrade scripts and see which tables have been added at each level of upgrade, working backwards until the scripts would not make any changes to the DB.

Also, we made a change to some of our sites that were hosted on a server that was upgraded to PHP 4.4 unexpectedly, and got them to run again by suppressing the errors. I will try to find out what changes we made and post them.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Paul Wilson

Wednesday 07 December 2005 1:26:52 pm

Thanks for your help Björn and Mark,

I used Björn's approach of checking thte contents of the file lib/version.php

For anyone else who strikes this problem, the version.php file contains information like the following immediately below the header/copyright message:

  \brief contains the eZ publish SDK version.

  define( "EZ_SDK_VERSION_MAJOR", 3 );
  define( "EZ_SDK_VERSION_MINOR", 0 );
  define( "EZ_SDK_VERSION_RELEASE", 2 );
  define( "EZ_SDK_VERSION_ALIAS", '3.0 release 2' );

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 20 2025 00:35:04
Script start
Timing: Jan 20 2025 00:35:04
Module start 'layout'
Timing: Jan 20 2025 00:35:04
Module start 'content'
Timing: Jan 20 2025 00:35:04
Module end 'content'
Timing: Jan 20 2025 00:35:04
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.0061 589.4063152.6563
Module start 'layout' 0.00610.0046 742.062539.5078
Module start 'content' 0.01070.0045 781.570393.3984
Module end 'content' 0.01520.0018 874.968834.3047
Script end 0.0170  909.2734 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002917.0968140.0002
Check MTime0.00127.1830140.0001
Mysql Total
Database connection0.00095.302710.0009
Mysqli_queries0.004224.988430.0014
Looping result0.00000.123510.0000
Template Total0.00148.210.0014
Template load0.00074.350010.0007
Template processing0.00073.832210.0007
Override
Cache load0.00052.813410.0005
General
dbfile0.00031.682580.0000
String conversion0.00000.060340.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