|Error Codes for Submissions|
The following list defines error codes you may see if there is an issue with your listing submission.
Please note, this page is under development, so be patient with these upgrades - it means we are working for you! :-)
A notice is required on each PHP file stating that the file is licensed GPL (or other compatible accepted license). We recommend a format similar to:
Security is extremely important in Open Source Software, so to help prevent execution of files outside of the framework, the following code is required in all of your PHP files:
An install file should include the license information:
All domains in your listing that use a version of the trademark in the URL, must be registered and approved prior to listing approval. Also, the disclaimer required must be clearly visible on your site. This includes domains that have Joo, Joom, Joomla or any similar portions in them. (Example: thejoomlasiteibuiltyesterday.com, thesiteofjoom.com, joodontknowjoomla.com, etc)
TM2-Extension Name Violation (Extension name is not registered with and approved by Open Source Matters)
The same restrictions for domain names also applies for Extension Names. However, using "Joomla XYZ Product" is not allowed (as of 2009). You may use MyProduct for Joomla as long as it's registered with OSM.
Using the Joomla logo and the requirements surrounding it's usage are often confusing. To help with this, we are working on a "Simple Guide to the Joomla! Trademark". In the meantime, read the information on Open Source Matters' website concerning Limited Use and Conditional Use logos and badges.
One way that a site can be exploited is through accessing folders directly. To help prevent this, all folders should have an index.html file (blank) in them. This way, if I navigate to site.com/components/com_myextension I will see a blank screen rather than the list of files in that folder.
Every extension must install/uninstall in a basic setup. This must work for both localhost and live sites.
Having a "clean upgrade path" is critical to both security and maintainability of a site. Extensions that "hack" the core or other extensions are not allowed. The only exception is if they perform the "hack" after backing up the original file, and then restore the original file on uninstall. As nearly every extension can be installed and many have built-in "add-on installers", hacks are frowned upon more and more. Additionally, it takes extra volunteer time to review these, so the approval time could be double the standard.
An extension that modifies folder and/or file permissions can be dangerous to a web site and server. While it is sometimes necessary to change permissions, this must be explained during the install process so that the end-user is aware of what you are doing to their files/server.
General listing errors don't often occur, however in the event that you see this code, make sure to check the notes included. If it is a special circumstance, you may receive an email from the team, but fee free to email with questions if this code is designated to your submission.
An important goal of the JED is to provide End Users with the ability to easily find solutions to their needs. To maintain consistency of listings, protect copyrights and enable brands to be built, we require that all Extension/Listing Names be unique and not too similar to others already in the directory.
Your download link must point directly to the download or product page. You may point directly to the file itself if you prefer if the link does not require registration. Download links may not point to "Extension Installers". If you offer multiple versions of your extension (for example, a non-GPL version and a GPL version) you must only point the "Download" link on your listing to a page that the version promoted is the one displayed on the JED.
For search enhancement and VEL compliance, listings must all contain the "Unique Install Information". This includes the "Installs As Name" (Example: Content - MyContentPlugin) and the "Filename" (Example: com_mygreatextension). This was implemented in this manner to help minimize the need to rename listings and to help ensure consistency when an extension is listed as vulnerable.
Every listing in the directory must comply with the GPL License (or whatever License Joomla! is distributed as - currently GPL v2). There are other licenses that are compatible with the GPL v2, and those are acceptable as well. Additionally, the JED does not allow "additional restrictions" on top of the GPL. For example, you cannot limit the usage of your extension to "X" number of domains. You may, however, sell "support" based on a limited number of domains.
As the JED grows, new opportunities and questions arise. One issue that plagues the JED and it's users is arriving at a site from a listing that is "Commercial" to find out that additional restrictions have been placed on the extension. To help monitor this, if your listing is commercial, you must include a link to your Terms and Conditions and/or your license agreement on your site.
LD1-Your listing description contains a foreign language
Listings are required to be in English. The use of any other language is not permitted.
LD2-Your listing description contains code, tags or syntax
Listings descriptions cannot contain code, syntax or tags as they often interfear with plugins we have installed.
NM1- Listing name does not match install name
Listing titles/names must match the install name (found in the install xml < name > < /name > )
NM2- Listing name does not follow the naming conventions for extension specific listings
Extension name for extensions specific extensions must be named "MyProduct for MainExtension" This naming convention is in place to help protect the extension names of the other developers. See http://docs.joomla.org/Extensions_name#Extension_Specific_Extensions