Upgrade from really an old version - problem

Author Message

J. T.

Monday 22 March 2010 3:51:53 pm

Hi experts.

With an old version of ez-pulish I think I got a big problem. It’s version number 3.44 and software to the website www.chronik-reportage.de. Hostmaster is 1&1. As somebody told me, 1&1 only works with higher versions of ez-publish. So I tried to upgrade.

No chance. After clicking the necessary button “check files” before upgrading, ez-publish tells me

“Warning, it is not safe to upgrade without checking the modifications done to the following files :
kernel/classes/datatypes/ezxmltext/handlers/output/ezxhtmlxmloutput.php”
I do not know where and how to. Do you?

As there would be lots of details to change after while upgrading: Is there maybe a different way to get texts online than to upgrade. Momentarily, every time I try to publish/put into frontend a text the message is “Fatal error: eZ publish did not finish its request. The execution of eZ publish was abruptly ended, the debug output is present below.”
Folders I can publish.

Can you maybe help me? You can get every further information needed. The website is result to a project of young people in Poland, Auschwitz. We try to remind several yet unpublished destinies of people in that former concentration camp. A modern site up to date would be great though not necessary. Publishing the news would be fine.

Thank you in advance,

T.

Marco Zinn

Tuesday 23 March 2010 3:35:55 pm

Hello J.T.

is the site beeing hosted at 1&1 in Germany?

You probably would need to upgrade to some ez 4.x version, so you can run it on PHP5 (which should be standard at all webhosters today)

From my experiences with upgrading, an upgrade von ez 3.4 to ez4 will drive you completely crazy and take you several hours. You will probably end up doing the design all over.

From some click through the current website, i can see, that ez crashes in some places when trying to display content... Thats really not the best place to start such a huge migration way.

Buttom line: Depening on the amount of content, you should think about doing the site completly new.

Doing a setup of eZ 4.x is something, where we (Hyperroad Design) could help you with. But you would end up with a lot of copy&paste work. From what i saw, most of your content is text, so this should be some manageble task.

Don't hesitate to contact us or reply here.

Marco
http://www.hyperroad-design.com

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 16:00:54
Script start
Timing: Jan 18 2025 16:00:54
Module start 'layout'
Timing: Jan 18 2025 16:00:54
Module start 'content'
Timing: Jan 18 2025 16:00:54
Module end 'content'
Timing: Jan 18 2025 16:00:54
Script end

Main resources:

Total runtime0.0178 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.0065 589.4766152.6406
Module start 'layout' 0.00650.0028 742.117239.4766
Module start 'content' 0.00930.0065 781.593889.5547
Module end 'content' 0.01570.0020 871.148434.3047
Script end 0.0177  905.4531 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002614.7589140.0002
Check MTime0.00126.8942140.0001
Mysql Total
Database connection0.00063.559010.0006
Mysqli_queries0.003519.476130.0012
Looping result0.00000.084510.0000
Template Total0.00179.710.0017
Template load0.00105.414310.0010
Template processing0.00084.249410.0008
Override
Cache load0.00073.979910.0007
General
dbfile0.00105.694480.0001
String conversion0.00000.050940.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