Tutorials for Magento and Joomla! - Yireo

Video: Magento Enterprise 1.6 to 1.7 upgrade

This video-tutorial shows you which steps you need to take to upgrade the Magento Enterprise Edition version 1.6 to version 1.7. This involves primarily a file patch - a procedure which could be applied to any Magento upgrade. But this will throw the error Invalid mode for clean() method. We will show how to fix this.

No downloader for Magento Enterprise

Magento Enterprise does not ship with a Magento downloader application.

The Magento Community Edition ships with a separate MagentoConnect manager. This makes it possible to upgrade Magento packages through a web-interface - the manager will automatically download the right updates. But the Magento Enterprise Edition doesn't ship with such an application. Even worse: You could kill your site if you use the community-version of MagentoConnect because that will also install community-updates, not enterprise-updates.

Patching Magento Enterprise Edition

Needless to say: You need a proper backup before doing this. Make sure you also know how to restore that backup, because a backup without restore procedure is also worthless.

The only solution to upgrade the enterprise-site is to patch the site. This could be done two ways: By setting up a fresh new site and copying all third party modifications to that site, or by patching the original. In this case we patched the original, which is more dangerous but much easier.

Invalid mode for clean() method

After the files have been upgraded, you'll need to login into the Magento Admin Panel. Unfortunately this will throw a PHP-error like the following:

Invalid mode for clean() method

To fix this, remove the folder app/code/core/Zend/Cache entirely. It is a left-over of the old Magento version, but because Magento loads its classes automatically this old left-over is still detected and used while it shouldn't. Just delete it.

Database changes

After patching the files, make sure you refresh the Configuration Cache. Each Magento module could be shipped with a PHP-script to update the SQL-database. But because the Configuration Cache caches the XML-configuration of modules (including the version) these SQL-updates will not be applied unless you flush the cache.