Upgrade eZ Publish 4.3 to latest version

guys,
I think that in this scenario we can skip some of this steps. For example upgrade from 2011.05 to 2011.06, 2011.06 to 2011.07 and 2011.07 to 2011.08 do nothing. This only changes kernel so I think that this step is not necessary. Especially when we do upgrade to version 2011.9 at the end of this process.
What do you think?

Thursday 27 October 2011 9:44:16 pm

guys,
I think that in this scenario we can skip some of this steps. For example upgrade from 2011.05 to 2011.06, 2011.06 to 2011.07 and 2011.07 to 2011.08 do nothing. This only changes kernel so I think that this step is not necessary. Especially when we do upgrade to version 2011.9 at the end of this process.
What do you think?

Hi Radek,

Every time only code-base changes are required (in other words : no DD schema modification or upgrade script to be run), we can safely skip the step to the next version.

Cheers,

Thursday 27 October 2011 10:06:20 pm

Hello Nicolas,

That is a great idea! Thank you for sharing!

This is something I will remember for the future.

"If the upgrade is code only (no sql or scripts required) then skip to the next version"

Cheers,

Heath

Friday 28 October 2011 8:36:45 am

Nicolas, thanks

So, upgrade from 4.3 to 2011.9 should contains only two seps:

1. Upgrade form 4.3 to 4.6 (2011.7) http://doc.ez.no/eZ-Publish/Upgrading/Direct-upgrading/Direct-upgrading-to-4.6-from-4.1-4.2-4.3-and-4.4/Direct-upgrading-from-4.3-to-4.6

2. Upgrade form 2011.7 to 2011.9

And one big point - from 4.2011 to 2011.5- there is on extra tabel so don't forget to create it

btw, there is 2011.10 avaiable

Monday 02 July 2012 5:37:19 am

Upgrading via Packages from 4.4 to 4.6 (2011.10???) or to 4.7 (2012.X???) may be an option?

Is there a better explained tutorial for upgrading (the official upgrade tutorial here:

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.4-to-4.7

Looks incomplete to me, it does not state clear if I should rewrite files or make a new directory, and if the folders stated is all there is to be moved form example... Does not make me fell confident its an error free upgrade, looks like lots of possibilities to have problems in the way...

Anybody please advice. Thank you.

Wednesday 29 August 2012 9:07:57 pm

No one? Im stuck in the process... Is it a new install over the other or in a new directory?

Wednesday 29 August 2012 10:05:08 pm

Take a look at https://github.com/leidentech/ez-...l-tools/blob/master/convertscript.sh

This might help.

Edit: changed link to github repo.

Modified on Tuesday 05 February 2013 8:24:42 pm by Steven E Bailey

Thursday 30 August 2012 9:20:31 am

Sorry, that was a bit of an answer to a question that you weren't asking. This is maybe more an answer to what you were asking:

Before you do anything, check on the backend if any files have changed... if you have custom kernel changes then you will have to migrate them to the new site. Also, don't do this on a production machine - do it on a test machine first.

What I do is start fresh - move your old site out of the way and create a directory with the new basic ez install. Then copy your override and siteaccess directories to the settings folder. Copy any custom designs to the design directory (if appropriate) and custom extensions (if appropriate) to the new extension directory.

For ez bundled extensions (ezfind, ezjscore etc.), your best bet is to go with the new bundled extension - but - make sure you copy any changed settings from these directories to the new one.

Extensions like ezwebin and ezflow have their own upgrade instructions.

Copy, or move, your var/<VarDir> to the new installation. Copy them all if you have multiple.

Do a generate autoloads - or copy the files from autoload , var/autoload to the new installation.

Then you can follow the upgrade instructions.

Thursday 06 September 2012 7:00:29 pm

Steven, Thanks for your answer...

I will give it a try this way... I have lots of overrides all over... (one of the not confortable ez publish things for me).

For ezfLow, ezFind upgrades... are this done after or before moving files?

In the database, do I have to make any changes?

Thursday 06 September 2012 8:32:21 pm

I normally do the upgrade and make sure the site works (you get a connection and get content back) and then worry about the extensions. eZFind will probably be easy since it's just making sure the settings match - actually you better not just copy the settings over - depending on the version differences there may be more settings added which would be lost if you just replaced the new settings files with the old ones. You may also have to add additional sql from the extensions - I know ezfind added the ezfind_elevate_configuration table at some point. The best bet is to follow whatever upgrade instructions are appropriate for the extensions.

The core database changes will be done when following the instructions Heath posted or with the convert script I provided (which you should only actually use if you understand what it does) - there is also an extension http://projects.ez.no/ezupgrade but it looks like the upgrades stop at 4.4.

Upgrade eZ Publish 4.3 to latest version

Forums menu