This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » Install & configuration » Upgrading from 4.3 to 2012.4
expandshrink

Upgrading from 4.3 to 2012.4

Upgrading from 4.3 to 2012.4

Wednesday 09 May 2012 3:29:56 pm - 6 replies

Hello,

I would like to upgrade my server configuration (apache 2.4+php 5.4) and I saw that I need to upgrade ez. I'm currently with 4.3 (+ezfind).

Is the upgrade process the same with this version gap ? Upgrade db, upgrade files, clean cache, done ?

Thank you

Wednesday 09 May 2012 3:40:39 pm

Hi Michaël, 

You need to first upgrade to 4.4, then follow every single upgrade instruction between the 4.2011 version and the latest, 2012.4. When there is no database-level change between two eZ Publish Community Project versions, you can safely hop over to the next eZ CP version.

Cheers,

Friday 11 May 2012 10:26:44 am

I think that the update process should be cumulative, we just can't spend our time on updating+testing ez every month.

Monday 16 July 2012 5:59:14 pm

Quote from Nicolas Pastorino :

You need to first upgrade to 4.4, then follow every single upgrade instruction between the 4.2011 version and the latest, 2012.4. [...]

Hi Nicolas,

Are you saying that it is *not* recommanded to follow the Entreprise version "Direct Upgrade" guides ?

I must confess that I'd fancy identifying the "almost the same as the Entreprise 4.6 version" Community Project version (seems to me that the likely candidate is the 2011.5, as a "4.6 stable +/pre-4.7" version (*)) and do the straight jump from 4.1.4 according to the Entreprise update docs [1].

Or make a leap of faith and jump from 4.1.4 to 2012.5 as the first "unstable stable 4.7/not yet a 5.0" following the guidelines of the Entreprise update docs [2].

I need an aspirin.

(*) : I'm totally guessing here, since I haven't found yet the "version map" mentionned in the "Community Project Release Policy" slides [3] and I'm just guessing from the content of the "update/common" and "update/database/mysql" directories.

[1] http://doc.ez.no/eZ-Publish/Upgrading/Direct-upgrading/Direct-upgrading-to-4.6-from-4.1-4.2-4.3-and-4.4

[2] http://doc.ez.no/eZ-Publish/Upgrading/Direct-upgrading/Direct-upgrading-to-4.7-from-4.1-4.2-4.3-4.4-and-4.5/Direct-upgrading-from-4.1-to-4.7

[3] http://share.ez.no/community-project/release-policy

Regards.

Monday 16 July 2012 10:31:02 pm

@Richard have you seen this? http://pubsvn.ez.no/ezpublish_version_history/index.php The mapping between versions you make by drawing straight vertical lines...

Monday 16 July 2012 10:32:42 pm

@Michaël you are welcome to participate in improving this situation.

The 1st step would be to submit patches to ezpublishbuilder (on projects.ez.no) to improve automation of the build process...

Tuesday 17 July 2012 9:59:14 am

@Gaetano> actually no, I didn't come to my mind to check pubsvn.ez.no (I thought the server was long gone since the move to github).

Thanks for the link that clarifies the version mapping between Entreprise version and Community Project, it confirms what I had determined from hints here and there.

The only occurence of this link is on a post of Robin Muilwijk which answers the precise question of the correspondance between Entreprise and Community Project version numbers, so I will probably crosspost the link in the "Community Project Release Policy" article too (to help people and Google find it).

For my migration problem, I will probably follow this road :
4.0.6 -> 4.0.7 ( http://doc.ez.no/eZ-Publish/Upgrading/Upgrading-to-4.0/from-4.0.x-to-4.0.y )
4.0.7 -> 4.1.4 ( http://doc.ez.no/eZ-Publish/Upgrading/Upgrading-to-4.1/4.0.x-to-4.1.y )
And then jump straight from 4.1.4 to Community Project, following the Entreprise version direct upgrade guidelines :
4.1.4 -> 2012.5 ( http://doc.ez.no/eZ-Publish/Upgrading/Direct-upgrading/Direct-upgrading-to-4.7-from-4.1-4.2-4.3-4.4-and-4.5 )
+ add the "not already done" specific upgrading instructions from 2012.4 to 2012.5 (which should correspond to importing the sql files in "update/database/<driver>/<4.7 or 5.0>/unstable" so as to have a consistent eZ Publish version number of "5.0.0alpha1"blunk.gif Emoticon.

Thanks a lot Gaetano,
Best regards.

expandshrink

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

36 542 Users on board!

Forums menu

Proudly Developed with from