Upgrade from eZ Publish 3.x to 4.x issues

«

Previous topic

|

|

Next topic

»

Author	Message
Piotrek Karaś	Monday 08 October 2007 11:15:39 am Maybe it is little early to ask this question, but I bet it will become an issue very soon and at least a hypothetical answer should exist by now. <b>Is a relatively easy upgrade from 3.x to 4.x meant to be possible or planned?</b> If I put the facts together right, the early 4.x will be nothing more than 3.10 for PHP5. Shouldn't that mean that 3.x upgrade or at least some automated structure and content transfer should be possible? <i>This information may be especially valuable for people who expect a soon PHP4 withdrawal.</i> -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Paul Borgermans	Monday 08 October 2007 12:33:26 pm Hi Piotrek Upgrade is fairly easy: just follow the instructions up and until 3.10: database upgrades and scripts to run. As in previous releases, you may need to do that from release to release if coming from quite old eZ Publish versions. I upgraded a few already to find bugs (3.8 and 3.9 based sites), no problems encountered thusfar. I ran all the upgrade scripts within eZ Publish 4.0alpha1. An important requirement though (and which was good practise anyway before): database and templates should be UTF-8 An easy transition was one of the goals of this release! Regards Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Piotrek Karaś	Monday 08 October 2007 12:54:39 pm Hello Paul, Thank you for your reply. So I expected, but now it's confirmed. I'm still little reluctant to applying multiple subsequent upgrades since we've encountered several post-upgrade problems in the past, and I am only talking direct x.x.1->x.x.2 sort of upgrades. But there's a chance we did something wrong - it was quite some time ago. Still, if there's no major change, that's a good point to start working on the upgrades or exports. Luckily, we've never had or wanted to change UTF-8 to anything else, so that's some help. Can't wait for stable 4 ;) <i>Greetings</i> -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
SatyaPrasad Alamuru	Tuesday 13 November 2007 4:47:31 am We are developing a website for one of our clients using eZ Publish 3.9.3 and have to migrate to PHP5. We want to find out about the effort involved in migrating eZ Publish from 3.9.3 to 4.0 (as it is supposed to work with PHP5). Currently we are using the extension “Oracle Database 1.4” as the DB is Oracle. Here is the list of questions we have 1. What is the exact time line for the production release of eZ Publish 4.0 (currently road map states early 2008)? If the time line is not known now, Can we get an idea by when the exact time lines will be made official? 2. Will Oracle be supported by eZ Publish 4.0, as it is stated in the migration steps from 3.10 to 4.0 as “The eZ Publish Extension for Oracle® Database v1.5 and earlier (plus the upcoming version 1.6) do not work with eZ Publish 4.0.0 alpha2. Do not upgrade to 4.0 if your site makes use of this extension.” (mentioned in the URL - http://ez.no/doc/ez_publish/upgra...grading_to_4_0/from_3_10_0_to_4_0_0) 3. Currently we are in the development phase of the project, given the tentative time line of 4.0 release, what should be the recommended approach? Should we upgrade to 3.10.0 and go to production and then think of upgrading to 4.0? Or we upgrade to 4.0 and then go to production? Any response to the above questions will be highly appreciated. EDIT: this question can be answered here: http://ez.no/developer/forum/developer/upgrade_from_ez_publish_3_9_3_to_4_0#msg153040

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 31 2025 04:25:33
Script start
Timing:	Jan 31 2025 04:25:33
Module start 'layout'
Timing:	Jan 31 2025 04:25:33
Module start 'content'
Timing:	Jan 31 2025 04:25:33
Module end 'content'
Timing:	Jan 31 2025 04:25:33
Script end

Main resources:

Total runtime	0.0161 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	588.2578	151.2266
Module start 'layout'	0.0044	0.0029	739.4844	36.6797
Module start 'content'	0.0073	0.0073	776.1641	94.1563
Module end 'content'	0.0146	0.0014	870.3203	37.9922
Script end	0.0161		908.3125

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	16.2539	14	0.0002
Check MTime	0.0012	7.6516	14	0.0001
Mysql Total
Database connection	0.0007	4.0498	1	0.0007
Mysqli_queries	0.0024	14.8892	3	0.0008
Looping result	0.0000	0.0872	1	0.0000
Template Total	0.0011	6.8	1	0.0011
Template load	0.0009	5.2829	1	0.0009
Template processing	0.0002	1.4697	1	0.0002
Override
Cache load	0.0006	3.4865	1	0.0006
General
dbfile	0.0024	14.7635	8	0.0003
String conversion	0.0000	0.0355	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs