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.


GL1 - General listing error

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.


LC1 - Licensing violation

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.


LC2 - Extension is Paid, but doesn’t include a link to a terms of service or license agreement

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.


LC3 - License link does not mention extensions

The license link provided does not mention an extension. Your license page should reference specifically how your extensions are licensed.


LC4 - Invalid license type

Extensions are required to be GNU/GPL or AGPL licensed. LGPL is for library extensions only. Any other license type is unacceptable.


LK1 - Invalid project link

Project links need to point to the developer’s main site. Links to social media are not permitted.


LK2 - Invalid download link

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.


LK3 - Demo link points to a production site

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.


LK4 - Invalid documentation link

Documentation links need to point to actual documents about the extension. This field is optional and can be left blank.


LK5 - Invalid license link

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.”


LK6 - Invalid support link

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.


MK1 - Unapproved marketing techniques

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.


PE1 - Internal processing error

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.


PH1 - Headers missing GPL license notice

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&


PH2 - Files missing JEXEC security

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' ); 

PH3 - License tag missing or incorrect in the XML install file

The XML manifest of the extension does not include the license of the extension. For instance, this is a valid license tag:



NM1 - Listing name does not match install name

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.


NM2 - Listing name does not follow naming conventions for extension-specific listings

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.


NM3 - Listing name contains “module” or “plugin”

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.


NM4 - Name/Title is a description

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.


NM5 - Version in name/title

Versions are not permitted in names (for example: My Extension Version 1.3).


NM6 - Name already taken

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.


TM1 - Domain Violation

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:,,, etc.).


TM2 - Extension Name Violation

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.


TM3 - Logo Usage Violation

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 for more details.


TM4 - Name/title contains a registered trademark

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.


TM5 - Improper fork

The listing does not meet guidelines for forked extensions. See the rules for Forked Extensions for more details.


SE2 - Extension does not install/uninstall on a basic setup

Every extension must install/uninstall in a basic setup. This must work on all current Joomla versions you indicate in your listing details.


SE3 - Extension is a hack

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.


SE4 - Extension modifies the permissions of files/folders without warning

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.


SY1 - Internal System Error

There was a system error that prevented your submission from being processed automatically. Please open a support ticket.


XM1 - License tag missing or incorrect in XML install file(s)

All install files should include the license information. In the install XML file: <license> GPL Version </license>


ZP1 - ZIP Archive Failure

Your .zip file is not packaged properly or is corrupt and cannot be opened.


ER1 - Error Reporting Disabled

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.


US1 - Update Servers missing or incorrect in XML file(s).

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.