I need to package an extension for Magento Connect and I'm in doubt about following points:

  • Do I need EE to package it ?
  • Should I use a different 'Channel' ( instead of community ) ?
  • Any other difference instead of packaging an ext. for CE ?


It is advisable to upload the package for Connect 1.0

Once you upload the package on Magento Connect, It will try to convert the package from 2.0 -> 1.0
This process return an error while conversion from 1.0 -> 2.0 works


The reason behind this question is the following:

Suppose I want to sell the extension and so my customer will download the package file from my store.

If they don't have the community channel installed:

  1. the installation will fail with the following message:

    CONNECT ERROR: The 'community' channel is not installed. Please use the MAGE shell script to install the 'community' channel.

  2. the store will go in maintenance mode
  3. the client will go in panic.
Even if the above issue can be easily solved running this command: ./mage mage-setup . ... this doesn't look like a plug and play solution and potentially can create damage to a store.

So the point is:

there is any more proper way to deliver a non-free extension for EE ?

  • 1
    IIRC Just bear in mind that you can't upload an extension for EE if you are not an industry partner. May 2, 2013 at 7:40
  • Thanks @sonassi however this is not the scenario.
    – Fra
    Jul 22, 2013 at 10:23

1 Answer 1


The answer is 'No', to all of your 3 questions. The extension packer is just an UI for selecting the files of your extension and making an archive compatible with Magento Connect.
It makes no difference if the extension is for CE or EE. The version (CE/EE) will be specified when you add the extension on magento connect.

  • I have temporary removed the 'accepted' flag as it is not clear if you answer is complete, what about this issue: CONNECT ERROR: The 'community' channel is not installed. Please use the MAGE shell script to install the 'community' channel.
    – Fra
    Jul 22, 2013 at 8:30
  • I'm getting this issue if I install the ext. uploading the package file directly in the backend, looks like EE has another default channel
    – Fra
    Jul 22, 2013 at 8:38
  • @Francesco I'm not sure if it's related, but I've been hearing murmurings from the community about problems with packaging extensions for connect lately: twitter.com/magentoconnect/status/358337868252454912 Jul 22, 2013 at 8:50
  • @AlanStorm Could this be related to the recent upgrade on their website (including Magento Connect)?
    – Marius
    Jul 22, 2013 at 8:53
  • 2
    @Francesco It's been years since I managed an enterprise edition installation, but mage-setup was always a standard part of getting a system up and running. Also possibly relevant to your interests: info.magento.com/rs/magentocommerce/images/… Jul 22, 2013 at 11:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.