Magento Connect FAQ
UPDATE: Official Magento Connect Guidelines can be found here.
- We are now tweeting new extensions through our @Magento Connect twitter account as they get approved. Keep in mind that the title of your extension, and the brief description will tweet out with a link directly to your extension on Magento Connect. Please do not use links in the brief description. Add meaningful descriptions that you want to see through tweets and search results. If you add links to your brief description, we cannot approve it. (Updated 9/7/11)
- Do not attempt to upload an extension with Stability = Development. We are unable to approve these on our end because they are used for testing purposes only. Please package only in Alpha, Beta or Stable to add your extension to Magento Connect.
- Please be aware of our Extension Guidelines
- Please make sure you read the section on Broader Extension Support before uploading your extensions.
- When packaging an extension, the system generates a package.xml inside the tar file. This file is needed to properly upload the extension, categorize it, make sure it’s listed on the developer profile page. There are several things which may set off an “Invalid Package.xml” error if this file is not generated properly. Please be sure that the details generated from packaging process on the back-end correctly reflect the information of the account holder uploading the extension.
- * For example: Only the person uploading the extension should be listed on the first line in Authors. The email and username (not screename)inside the package.xml must match the account which is uploading the extension.
Your most common Magento Connect Questions - Answered and explained. Stay tuned for more updates as they become available.
Magento Connect is a marketplace that allows Magento community members and partners to share their open source or commercial (for-profit) contributions for Magento with the community. Read More
There is a small amount of starter documentation available on our Wiki under the Modules and Development Section.
Anyone can create extensions and upload extensions to the marketplace directly from their magentocommerce.com account. Simply click on My Account after logging into Magento, and click on the “Developers” option. From here you can add or manage your Magento Connect extensions.
When you click on “Add New Extension” you have the option to create a free or paid extension profile. The difference between free and paid is that we can host free community extensions for you directly on our site. Merchants are able to get the extension key for the free community extension through the Magento Connect marketplace. Paid extensions are purchased and sold directly from the developer website, using a link to the landing page from the Magento Connect Marketplace extension profile.
If your extension is listed as not approved, then chances are it did not meet the guidelines specified for extension approval listed here: Magento Connect Extension Guidelines. If you have adhered to all the guidelines but your extension is still listed as not approved, contact me directly for further explanation.
If your extension has an “Incomplete” status attached to it, it means that your free community extension didn’t upload properly. You’ll need to repackage the extension using a new version number and attempt to upload an update under the existing extension name. You must change the version number in order to successfully update the extension.
Most extensions are created by 3rd party developers, who support their own extensions. What Magento provides is a searchable indexed directory allowing developers, merchants and partners to find all Magento Extensions from one centralized location. If you have a question about a particular extension, contact the developer directly through the extension profile by clicking on the link “View Developer Profile”.
The packaging process has changed a bit from 1.4 to 1.5 and there are some significant differences that we’ve detailed in the following blog post: http://www.magentocommerce.com/blog/comments/developers-packaging-extensions-in-magento-15-explained/ You can also refer directly to our packaging instructions:
If you are on a Magento shop prior to 1.5, you must use extensions labeled as 1.0. Systems 1.5 and later use the 2.0 extensions. With this new 2.0 version, we’re introducing support for dependencies. This support allows you to be able to install extensions and also be alerted of important information on why the new extension may interfere with a previously installed extension or possible prerequisites in order to make the new extension function properly. Read More
In order to allow more support for developers who want to control which versions of Magento they support - we no longer auto generate the 2.0 extension key. Developers must actually physically check that they’d like to support their extension with 1.5 during the extension creation/editing process. read More
This part of our FAQ details common packaging, uploading and install errors.
This error means you’re trying to install a 2.0 extension on a version of Magento prior to 1.5. If you are on Magento prior to 1.5 you must use 1.0 extensions.
This means there was an error in the packaging. Make sure you’re using the correct channel and check our blog for the most common mistakes: Packaging Extensions in 1.5
This error means that you may have mistakenly attempted to package your extension with your SCREEN name and not your USER NAME. Please be aware that you must use the registered “user name” to package an extension.
This error usually means that you are attempting to install an extension is in Alpha or Beta. 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.
This error happens when the packaged extension name is different than the name you use on your extension profile for Magento connect. You must use the same extension name when creating the profile as you did when packaging the extension.
This error sometimes happens when attempting to install a 2.0 extension. This may be a server configuration issue which prevents data transfer to the server. As result of POST request with “http://” text in any field of the query browser gets response 403 Forbidden. Ask your hosting provider to reduce the impact on the transmitted data between the server and a visitor’s browser.
Remove the http:// from the 2.0 extension key and attempt to install the extension that way.
This error happens if you don’t have appropriate permissions on your file folders. If you wish to use our web based downloader (Magento Connect Manager) for installation, upgrades or to install MagentoConnect extensions, you are required have write permissions on ALL Magento files (including the root Magento folder.) Read More
This error means that you are attempting to upload an extension which was packaged under an incorrect user name. Please be sure to package under your user name and not screen name.
If you have any questions, feel free to email me directly at connect at magento dot com.