The following list defines error codes you may see if there is an issue with your listing submission.
Please use the JEDchecker tool to screen your extension before resubmitting.
General listing don’t occur often. Please see the notes left by the JED team member. In special circumstances, you may also receive an email from a JED team member. Feel free to contact us, by opening a support ticket from the listings page if you have received the GL1 error message and you would like more details.
Every listing must comply with the current GPL License that Joomla is distributed as. Currently, Joomla is distributed using 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 limited 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 its users is arriving at a site from a listing that is "Paid" only to find out that additional restrictions have been placed on the extension. To help monitor this, if your listing is Paid, you must include a link to your terms of service or license agreement.
The license link provided does not mention an extension. Your license page should reference specifically how your extensions are licensed.
Extensions are required to be GNU/GPL or AGPL licensed. LGPL is for library extensions only. Any other license type is unacceptable.
Project links need to point to the developer’s main site. Links to social media are not permitted.
Download links must point directly to the download or product page. You may point directly to the file itself if registration isn’t required. Download links may not point to "Extension Installers". If you offer multiple versions of an extension (for example, a Paid version and a Free 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.
Links pointing to distribution sites that also distribute non-GPL Joomla extensions will not be accepted.
Demo links can only point to a non-production website. It has to be an actual demo and not a live site. This field is optional and can be left blank.
Documentation links need to point to actual documents about the extension. This field is optional and can be left blank.
Paid extensions require a link to the developer’s license on their site. Links pointing to the GPL website are not acceptable. The requirement is to ensure you aren’t adding any additional restrictions on top of the GPL. The page on your site can be as simple as “Our extensions are published under the GNU/GPL.”
Support links need to point to a ticket system, forum or any other type of support system. This field is optional and can be left blank.
Promotional text (i.e. “free”) is used in the listing or a listing that is posted as non-commercial even though the extension is commercial is not permitted. If a user is required to make a payment, like, or tweet at any point in order to use the extension it must be marked as paid.
There has been an internal processing error with your file attachment. Please open a support ticket so the JED Team can review your listing and determine if any further action is needed from you.
A notice is required in the header each PHP file stating that the file is licensed GPL (or other compatible accepted license). We recommend a format similar to:
// Licensed under the GPL v2&
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 unless they are external library files:
// no direct access defined( '_JEXEC' ) or die( 'Restricted access' );
Listing titles/names must match the install name. Found in the install xml as:
<name>Your awesome extension name</name>
Using a language string for a name is not recommended.
Extension names for extensions-specific extensions must include the name of the extension that it is meant to be used with. This naming convention is in place to help protect the extension names of the other developers.
See the rules for Extension Names for more details. You will need to open a support ticket from the page of the extension in question to request the name field to be updated.
Extension names cannot contain the words “module” or “plugin”. See the rules for Extension Names for more details. You will need to open a support ticket from the page of the extension in question to request the name field to be updated.
Names/titles shouldn’t be a description. See the rules for Extension Names for more details. You will need to open a support ticket from the page of the extension in question to request the name field to be updated.
Versions are not permitted in names (for example: My Extension Version 1.3).
An important goal of the JED is to provide end users with the ability to find solutions easily. 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.
All domains in your listing that use a version of the trademark in the URL, must be registered and approved by Open Source Matters prior to listing approval. Also, the disclaimer required must be clearly visible on your site. This includes domains that have Joo, Joom, Joomla or something similar (for example: thejoomlasiteibuiltyesterday.com, thesiteofjoom.com, joodontknowjoomla.com, etc.).
The same restrictions for domain names also apply for extension names. All extension names in your listing that use a version of the trademark in the URL, must be registered and approved by Open Source Matters prior to listing approval. 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 its 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 the Joomla! name and logo use. See http://opensourcematters.org/joomla-name-and-logo-use-requests.html for more details.
The extension name contains trademarked name (for example: Instagram, Dropbox, Google, Adsense, etc). The extension description should mention that trademarked names are only acceptable if the developer opens a support ticket against the submission and provides proof of authorization from the trademark holder.
The listing does not meet guidelines for forked extensions. See the rules for Forked Extensions for more details.
Every extension must install/uninstall in a basic setup. This must work on all current Joomla versions you indicate in your listing details.
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 restoring 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 increase greatly.
An extension that modifies folder and/or file permissions can be dangerous to a website and/or 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 the extension is doing to their files/server.
There was a system error that prevented your submission from being processed automatically. Please open a support ticket.
All install files should include the license information. In the install XML file: <license> GPL Version </license>
Your .zip file is not packaged properly or is corrupt and cannot be opened.
Your extension disables Error Reporting. Core Joomla has a function in the Global Configuration to disable Error Reporting. Disabling it globally from your extension files is not recommended.
The update servers tag in your XML file(s) is missing or incorrect. This is a requirement of all extensions uploaded after 10th January 2017.