Is there a extension/system upgrade manager in the development pipe ?

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
H-Works Agency	Monday 14 June 2010 3:49:02 am Hello everyone, Like every year i make my little post about having a upgrade manager inside ezpublish. To make my post short it will work the same way as Magento Connect for magento. A topic that, in my opinion, is growing more and more critical over the years as ezpublish versions continues to grow up. Its now officially a total nightmare to migrate a 3.8.1 website to a 4.2.0 for exemple. If you want to do thing cleanly you will have to install 4 or 5 different ezpublish, each with a different database and you'll loose a full day doing a 1mb content website upgrade. This functionnality - and a little graphical web 2.0 style change - would reposition ezpublish in the race with wordpress and other CMS. EZP is Great
Erland Flaten	Monday 14 June 2010 5:12:10 am Agree! Erland Flaten Lilllehammer, Norway
André R.	Monday 14 June 2010 5:52:08 am Tried projects like this? http://projects.ez.no/ezupgrade eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Erland Flaten	Tuesday 15 June 2010 4:56:39 am Looks nice :) I want to upgrade a site from 4.1.3 to 4.3 and I will try if ezupgrade (together with ezcopy) is less difficult. Erland Flaten Lilllehammer, Norway
H-Works Agency	Wednesday 19 January 2011 3:05:37 am Hello, eZUpgrade & ezcopy are both beta. The upgrade manager has to be part of ezpublish distribution. It's very strange ezp developers aren't asking for this functionality too much. EZP is Great

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 01:07:04
Script start
Timing:	Jan 18 2025 01:07:04
Module start 'layout'
Timing:	Jan 18 2025 01:07:04
Module start 'content'
Timing:	Jan 18 2025 01:07:04
Module end 'content'
Timing:	Jan 18 2025 01:07:04
Script end

Main resources:

Total runtime	0.0162 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.0057	589.5156	152.6875
Module start 'layout'	0.0057	0.0031	742.2031	39.5234
Module start 'content'	0.0089	0.0052	781.7266	93.5234
Module end 'content'	0.0141	0.0021	875.2500	34.3047
Script end	0.0161		909.5547

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.2688	14	0.0002
Check MTime	0.0011	6.7633	14	0.0001
Mysql Total
Database connection	0.0009	5.5710	1	0.0009
Mysqli_queries	0.0030	18.3476	3	0.0010
Looping result	0.0000	0.0870	1	0.0000
Template Total	0.0016	10.1	1	0.0016
Template load	0.0009	5.3780	1	0.0009
Template processing	0.0008	4.6971	1	0.0008
Override
Cache load	0.0006	3.8702	1	0.0006
General
dbfile	0.0008	4.9948	8	0.0001
String conversion	0.0000	0.0619	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