Posting in the Magento forums has been disabled pending the implementation of a new and improved forum solution which should better serve the community.

For new questions please post at magento.stackexchange.com, the community-run support site for the Magento community. We will be providing updates on the new forum solution soon. For questions or concerns please email community@magento.com.

Magento Forum

Packaging Extensions in Magento 1.5 Info for Developers/Merchants -Explained
 
Rhonda_Rondeau
Enthusiast
 
Total Posts:  924
Joined:  2010-08-03
Culver City
 

Packaging Extensions in Magento 1.5 Info for developers and also merchants:

http://www.magentocommerce.com/blog/comments/developers-packaging-extensions-in-magento-15-explained/

This blog mostly explains changes for developers but if you scroll down you can read about beta vs. stable extensions and the differences between 1.0 and 2.0

It’s a good blog for anyone using Magento Connect. Text below:

~_~_~_~_~_~_~_

Greetings Magento Community,

We’ve made changes on Magento 1.5 and there are some important changes for developers and merchants using Magento Connect should be aware of.
Packaging Extensions on 1.5

Packaging Extensions

Packaging extensions using 1.5 has some minor syntactical changes from previous versions. Please see our new documentation on packaging an extension using Magento 1.5.

The significant changes are:

* When packaging extensions, the channel field now uses the single word community. Extensions packaged prior to 1.5 use the words magento-community in the channel field.
* When packaging an extension, you now have the option to package your extension for Magento shops that are 1.5.0.0 & later version (2.0) or for shops pre 1.5.0.0. (1.0)
* When you click on the Save data and Create Package button to generate the tar.gz package file, the 2.0 extension file is now created in the var/connect directory. The 1.0 extension file is generated in the var/pear directory. This means there are two individual files - one for 1.0 and one for 2.0.

IMPORTANT NOTE: For broader extension support for free (unpaid) community extensions, it is best to package using pre-1.5.0.0 option. When uploading the 1.0 version from var/pear—Magento Connect will make the 2.0 version for you. If you wish to only support 1.5 and higher versions of Magento only then only upload the 2.0 file from the var/connect directory to Magento. If you are trying to create separate packages (such as to upload both a 1.0 and 2.0 version to your site for a PAID extension, or if you want different version numbers for different releases) then you must select both options when packaging which generates both 1.0 and 2.0 file types.

Make sure that you add this information to your extension description so that merchants are aware of the supported versions of your extensions.

Additionally, if you have previously uploaded a 1.5+ (2.0 only) extension and would like it to have support for Pre 1.5 (1.0) as well, repackage the existing extension with a new version number but be sure to upload the file from the var/pear directory when adding to Magento Connect. This will update both versions but also give you a 1.0 version fro Pre 1.5.
Incomplete Extension Information

Pending/Incomplete Status
If you have previously attempted to upload an extension and that extension is listed as pending/incomplete, you can still recover this extension by properly packaging the extension using a new version number and uploading the update under the existing extension.You cannot use the same version number.
What’s the difference between 1.0 and 2.0 Extensions?

1.0 and 2.0 - What is the Difference?

You may have noticed that Magento Connect Marketplace now has both 1.0 and 2.0 extensions. If you are on a Magento shop prior to 1.5, use extensions labeled as 1.0. Systems 1.5 and later use the 2.0 extensions. It is important to be aware of the differences.
Beta vs. Stable Extensions

Alpha vs. Beta Extensions

If you package and uploaded a Beta or Alpha extension - please add this information into the extension description. It’s important for the community to be aware that they’ll need to change their stability settings on the back-end of Magento Connect Manager. Magento Connect Manager’s Preferred State defaults to “Stable” extensions and attempting to install a beta extension with this setting results in a “Not Detected” error message as the system is not detecting the Stable extension.

To change this setting:

1. Select System->Configuration-> from your store’s admin panel.
2. Log into Magento Connect
3. Click the Settings tab
4. Use the pull-down menu to select your perferred state (stable, alpha, beta)
5. Click Save

If you have any questions about Magento Connect or looking for updated information, stay tuned to this forum. This forum has all the latest information on extensions, guidelines, as well as any issues that you as a developer, may need to be aware of.

As always, feel free to contact me directly if you have any questions.

Rhonda

 
Magento Community Magento Community
Magento Community
Magento Community
 
niro
Mentor
 
Avatar
Total Posts:  1609
Joined:  2009-03-04
Latvia, Riga
 
Rhonda_Rondeau - 14 March 2011 01:52 PM

IMPORTANT NOTE: For broader extension support for free (unpaid) community extensions, it is best to package using pre-1.5.0.0 option. When uploading the 1.0 version from var/pear—Magento Connect will make the 2.0 version for you. If you wish to only support 1.5 and higher versions of Magento only then only upload the 2.0 file from the var/connect directory to Magento. If you are trying to create separate packages (such as to upload both a 1.0 and 2.0 version to your site for a PAID extension, or if you want different version numbers for different releases) then you must select both options when packaging which generates both 1.0 and 2.0 file types.

This does not work anymore? All my modules are available only in version 1.0, but earler there was both versions (1.0 and 2.0).
It’s a error or i need to reupload all my modules for both versions? And how i do it (there is only one field for package upload)?

 
Magento Community Magento Community
Magento Community
Magento Community
 
Rhonda_Rondeau
Enthusiast
 
Total Posts:  924
Joined:  2010-08-03
Culver City
 
niro - 11 August 2011 09:21 AM

Rhonda_Rondeau - 14 March 2011 01:52 PM

IMPORTANT NOTE: For broader extension support for free (unpaid) community extensions, it is best to package using pre-1.5.0.0 option. When uploading the 1.0 version from var/pear—Magento Connect will make the 2.0 version for you. If you wish to only support 1.5 and higher versions of Magento only then only upload the 2.0 file from the var/connect directory to Magento. If you are trying to create separate packages (such as to upload both a 1.0 and 2.0 version to your site for a PAID extension, or if you want different version numbers for different releases) then you must select both options when packaging which generates both 1.0 and 2.0 file types.

This does not work anymore? All my modules are available only in version 1.0, but earler there was both versions (1.0 and 2.0).
It’s a error or i need to reupload all my modules for both versions? And how i do it (there is only one field for package upload)?

http://www.magentocommerce.com/blog/comments/magento-connect-extension-keys-update/s.

We’ve explained here. Please feel free to contact me directly if you have more questions

 
Magento Community Magento Community
Magento Community
Magento Community
Magento Community
Magento Community
Back to top