Question

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 ?

UPDATE:

Note:
It is advisable to upload the package for Connect 1.0

Explanation
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

UPDATE 2

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 ?

Was it helpful?

Solution

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.

Licensed under: CC-BY-SA with attribution
Not affiliated with magento.stackexchange
scroll top