Update to Version 1.4.3
| IMPORTANT !!! All users except admins will be deactivated an lose their permissions! Also the user-groups will be deleted. |
If you get a timeout near revision 1614-1616 please execute this script on the commandline:
<?php include_once("pimcore/cli/startup.php"); $classList = new Object_Class_List(); $classes = $classList->load(); if(is_array($classes)){ foreach($classes as $class){ $class->save(); } } $list = new Object_Fieldcollection_Definition_List(); $list = $list->load(); foreach ($list as $fc) { $fc->save(); } $list = new Object_Objectbrick_Definition_List(); $list = $list->load(); foreach ($list as $fc) { $fc->save(); }
Version 1.3.2 >= 1.4 (build 1046, 1113)
Build 1046
This build has a rather lengthy update script which might run into a timeout for projects with a lot of documents. If the update fails and your log tells you that the database update failed, please execute the following SQL statements manually:
update properties set name = "navigation_name_legacy" where name = "navigation_name"; update properties set name = "navigation_target_legacy" where name = "navigation_target"; update properties set name = "navigation_accesskey_legacy" where name = "navigation_accesskey_name"; update properties set name = "navigation_parameters_legacy" where name = "navigation_parameters"; update properties set name = "navigation_relation_legacy" where name = "navigation_relation"; update properties set name = "navigation_anchor_legacy" where name = "navigation_anchor"; update properties set name = "navigation_tabindex_legacy" where name = "navigation_tabindex"; update properties set name = "navigation_exclude_legacy" where name = "navigation_exclude"; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath,"navigation_name" as name, "text" as `type`, p.name as `data`, "0" as inheritable from documents_page p left join documents d on p.id = d.id where p.name is not null and p.name!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_name" as name, "text" as `type`, p.name as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.name is not null and p.name!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_target" as name, "text" as `type`, p.target as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.target is not null and p.target!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_accesskey" as name, "text" as `type`, p.accesskey as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.accesskey is not null and p.accesskey!=""; insert into properties select p.id as cid,"document" as ctype, concat(d.path, d.key) as cpath, "navigation_parameters" as name, "text" as `type`, p.parameters as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.parameters is not null and p.parameters!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_relation" as name, "text" as `type`, p.rel as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.rel is not null and p.rel!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_anchor" as name, "text" as `type`, p.anchor as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.anchor is not null and p.anchor!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_title" as name, "text" as `type`, p.title as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.title is not null and p.title!=""; insert into properties select p.id as cid, "document" as ctype, concat(d.path, d.key) as cpath, "navigation_tabindex" as name, "text" as `type`, p.tabindex as `data`, "0" as inheritable from documents_link p left join documents d on p.id = d.id where p.tabindex is not null and p.tabindex!=""; alter table documents_page change name DEPRECATED_name varchar(255); alter table documents_link change name DEPRECATED_name varchar(255); alter table documents_link change target DEPRECATED_target varchar(255); alter table documents_link change accesskey DEPRECATED_accesskey varchar(255); alter table documents_link change parameters DEPRECATED_parameters varchar(255); alter table documents_link change rel DEPRECATED_rel varchar(255) ; alter table documents_link change anchor DEPRECATED_anchor varchar(255); alter table documents_link change title DEPRECATED_title varchar(255); alter table documents_link change tabindex DEPRECATED_tabindex varchar(255);
If your log tells you that the database update succeeded, but the update failed due to a timeout, please execute the rest of the update script again, which is inlcuded in this cli script: build1046.php
Build 1070
The new extension manager has been activated. Please check if all your formerly installed plugins are activated in the extension manager. Older plugins (old definition of plugin.xml) might cause a failure in the activation.
Build 1113
Please note that with build 1113 the database engine was switched from MyIsam to InnoDB. If the project holds a lot of data the update to build 1113 might time out when executing the database changes. If this update fails, please check your database if all pimcore tables have been switched to InnoDB. In case they have not, please try the update again. Anyways, it is recommended to have a backup of your project before executing this update!
Version >= 1.2.1 (or >= build 566) to 1.3.0
The best, safest and most comfortable way is to use the next generation updater from version 1.3. This updater is fully comaptible to versions >= 1.2.1 (=> build 566). You can download the new updater here (http://www.pimcore.org/download/ng-updater-for-upgrades-to-1.3.zip)
After downloading just extract the contents of the package into the document root. If you are asked whether existing files should be overwritten, answer with yes. Of course you can also just copy/replace this 3 files (out of the package) manually to your /pimcore folder.
After replacing the files, reload or start the pimcore admin interface and go to "Extras -> Update" as usually. Then follow the steps in the update-wizard.
| IMPORTANT If you have installed the SearchPhp Plugin, please update this plugin to the latest version now. The backend search was moved to the core, without an update pimcore and the plugin might interfere with each other. |
| Update to >= 1.3.0 from a build < 566 If you want to update to >= 1.3.0 from a build below 566 please update first to the build 566. Then create an empty folder "system" in /website/var and make sure that the folder is writeable. After that insert the following line at the top of index.php: define("PIMCORE_SYSTEM_TEMP_DIRECTORY", $_SERVER["DOCUMENT_ROOT"] . "/website/var/system"); |
1.1.1 to 1.2.0
Because it was necessary to change some things in the updater, the update to 1.2.0 with the Liveupdater can fail, depending on the build your're updating from.
If the update fails, please follow this steps:
- Download the latest release from http://www.pimcore.org/download.
- Unzip and replace all contents in the /pimcore folder with the new ones.
- Open the file /pimcore/lib/Pimcore/Version.php and set public static $revision = 491;
Please replace 491 with the build number of pimcore before you performed the update. - Now login into pimcore and perform the update to 1.2.0 with the Liveupdater again.
1.0.8 to 1.1.0
Please use the Liveupdater, and update in small steps to 1.1.0, for example:
Start with an update to 360 and make the following steps between: 375, 399, 403, 420 and last but not least to build 468 (1.1.0).
If there is a problem such as "Warning: Missing argument 2 for Pimcore_Model_Abstract::setValue()" then open your database, open the properties_predefined table and change the column name "value" to "data".
Comments (1)
Nov 19, 2010
Vladimir Gilevich says:
When I tried to upgrade with memory_limit = 128M, I got error: Start updating t...When I tried to upgrade with memory_limit = 128M, I got error:
Start updating to build: 757
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 122084248 bytes) in /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php on line 609
PHP Stack trace:
PHP 1.
() /Library/WebServer/Documents/pimcore/pimcore/cli/update.php:0
PHP 2. Pimcore_Update::download() /Library/WebServer/Documents/pimcore/pimcore/cli/update.php:77
PHP 3. Pimcore_Update::getHttpData() /Library/WebServer/Documents/pimcore/pimcore/lib/Pimcore/Update.php:75
PHP 4. Zend_Http_Response->getBody() /Library/WebServer/Documents/pimcore/pimcore/lib/Pimcore/Update.php:364
PHP 5. Zend_Http_Response::decodeGzip() /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php:275
PHP 6. gzinflate() /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php:609
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 122084248 bytes) in /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php on line 609
Call Stack:
0.0008 657208 1.
() /Library/WebServer/Documents/pimcore/pimcore/cli/update.php:0
0.0142 2133376 2. Pimcore_Update::download() /Library/WebServer/Documents/pimcore/pimcore/cli/update.php:77
0.0145 2137928 3. Pimcore_Update::getHttpData() /Library/WebServer/Documents/pimcore/pimcore/lib/Pimcore/Update.php:75
19.0000 18940464 4. Zend_Http_Response->getBody() /Library/WebServer/Documents/pimcore/pimcore/lib/Pimcore/Update.php:364
39.8005 34201152 5. Zend_Http_Response::decodeGzip() /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php:275
39.8122 49461800 6. gzinflate() /Library/WebServer/Documents/pimcore/pimcore/lib/Zend/Http/Response.php:609
I was need increase memory_limit to 256M to have possibility run upgrade without problem.
Probably it will not bad to write in "System Requirements" about "memory_limit >= 256M" instead current "memory_limit >= 64M", or add note for "Upgrade Notes".
Thanks.