Magento Connect Manager Upgrade for Magento Community Edition

Magento Connect Manager 2.0 General Concept

For the Magento Community Edition users the new version of Magento Connect Manager (MCM), Magento Connect Manager 2.0, will become available. MCM 2.0 gives the possibility to install extension packages from the Magento Connect 2.0 channel server. The MCM 2.0 extension packages format differs from the previous MCM format, and the MCM 2.0 users will have the possibility to create extension packages in either old, or new version of MCM format, or both versions simultaneously.

In the new version of the MCM the mage shell script is used instead the pear shell script. But most commands are left without changes.

Upgrading the Magento Connect Manager

The main MCM upgrade features are the following:

  • The MCM can be upgraded without the entire system re-installation.
  • All installed extensions are saved in the new MCM version format automatically after the upgrade.

Upgrading the MCM is necessary for those Magento Community Edition users, who want to be able to upgrade the entire Magento system to the version 1.5. The possibility to return to the previous version of MCM is not previewed.

Upgrading using the MCM

To upgrade the Magento Connect Manager by means of the Magento Connect Manager itself you need to take the following steps:

  1. Log in to the Magento Admin Panel.
  2. On the top menu click System, point to Magento Connect, and then click Magento Connect Manager.
  3. Log in to the MCM. The Magento Connect Manager page opens.
  4. Click the Check for Upgrades button in the lower right corner of the page. The list of extensions to upgrade displays.
  5. Select Upgrade to 1.4.2.1 for the Mage_All_Latest extension. See screen shot below:

  1. Click the Commit Changes button. The extension is installed.
  2. Click the Refresh button.

The MCM is upgraded now, you are viewing the new version of MCM. All installed extensions are saved in the MCM 2.0 version format. They are displayed in one list under “Channel: Magento Community Edition”, as the extensions from the “connect.magentocommerce.com/core” channel are added to the “Magento Community Edition” channel in the MCM 2.0.

Upgrading the MCM using SSH shell access

To upgrade the MCM to MCM 2.0 using SSH shell access, you need to take the following steps:

  1. Log in to the server using SSH
  2. Go to the root directory of your Magento installation.
  3. Run:

./pear upgrade-all

  1. Run:

./mage sync-pear

Important note: Having upgraded the MCM to MCM 2.0 do not use pear script, use mage script instead.

Сreating extension packages in different MCM version formats

The procedure of creating the extension packages is left without changes, though you now have the possibility to choose the MCM version format for the created package.

To create an extension package archive you need to navigate to System > Magento Connect > Package extensions. On the New Extension page in the Package Info section the Package Format field is added, where you can select the format of the extension package. It can be Version 2.x, Version 1.x, or you can select both. See screen shot below:

The packages created in the Version 1.x format are stored in the magento/var/pear folder. The packages created in the Version 2.x format are stored in the magento/var/connect folder.

Loading local packages after upgrading Magento Community Edition

If you have upgraded the Magento Connect Manager first, and then upgraded the entire Magento system to version 1.5, you need to replace your extension package data files to be able to load them in the Magento Admin Panel.

To open the extension packages managing section, on the top menu click System, point to Magento Connect, and then click Package Extensions, the New Extension page opens. To load some local extension package data file, you need to navigate to the Load Local Package tab. See screen shot below:

If you have upgraded your MCM, and then upgraded the entire Magento system to version 1.5, there are no files in the list in the Load Local Package section. To make them available to system here you need to move the xml files manually from the magento/var/pear folder to the magento/var/connect folder.




 

Magento 2 GitHub Repository

Magento Job Board - Some sort of tag line goes here

Latest Posts| View all Jobs