Skip to content
Tutorials Center
My learning

Topics

Lesson 21 of 37 ยท Templates and Extensions

Extension Types and the Installer

Understand Joomla's six extension types, the Extension Manager, installation methods, update sites and the manifest file that describes every package.

Joomla's core is deliberately modest. Almost everything beyond articles, menus and users comes from extensions: add-on packages that you install, configure and update from the administrator. To use them wisely you need to know what kinds exist, how they are installed and what happens to your database when you do.

This lesson explains the extension types, the Extension Manager and the XML manifest that every package contains. Joomla cannot run in this site, so the screens are described by menu path and the TryIt blocks are small stand-ins: one that reads a manifest, and one that classifies extension types.

The extension types

Joomla recognizes these types. Each one has a different job and a different place in the interface.

Type What it is Typical example Managed under
Component A mini-application that owns a whole page's main output and its own database tables Articles (com_content), Contacts, a shop Components menu
Module A small block shown in a template position Login form (mod_login), menu (mod_menu) Content > Site Modules
Plugin Code that reacts to events; no screen of its own Editor, captcha, SEF handling System > Plugins
Template Page design and positions Cassiopeia System > Site Templates
Language Translated interface strings French, German System > Install > Languages
Library / File / Package Shared code, loose files, or a bundle of several extensions PHPMailer library, a package installing a component plus plugins System > Manage

A package is just a ZIP of ZIPs: one installation that installs, for example, a component, two modules and a plugin together. A single product from a third-party vendor is often a package.

Naming helps you read the database and the file system. Extension names carry a prefix: com_ for components, mod_ for modules, plg_ for plugins (with the plugin's group, such as plg_system_cache), tpl_ for templates, lib_ for libraries, pkg_ for packages.

flowchart TD
    P["Package pkg_shop"] --> C["Component com_shop"]
    P --> M["Module mod_shop_cart"]
    P --> G["Plugin plg_content_shop"]
    C -->|"owns"| T["Database tables #__shop_*"]
    M -->|"shows in"| S["Template position"]
    G -->|"listens to"| E["Events such as onContentPrepare"]

A package installs several extension types at once.

The Extension Manager

Everything about installing lives under System > Install (Joomla 4 and later; it was "Extensions > Manage" in version 3). The Extensions page offers three ways:

  1. Upload Package File: drag a ZIP from your computer. Good for purchased or downloaded extensions.
  2. Install from Folder: point to a directory on the server, useful for very large packages.
  3. Install from URL: Joomla downloads the ZIP itself. Only use a URL you trust, and prefer https.

Newer versions also include an Install from Web tab (the Joomla Extensions Directory) when enabled in the options. Whichever way you choose, you should see a green success message; if the upload fails the usual causes are PHP's upload_max_filesize / post_max_size limits, a temporary folder that is not writable, or a ZIP with the wrong structure.

After installing, find the extension: components appear in the Components menu, modules in Content > Site Modules (create a new module of that type), plugins under System > Plugins where you must usually enable them, because a plugin installs disabled in many cases.

Other tools in the same area:

  • System > Manage > Extensions lists everything installed, with filters by type and status. You can disable an extension without losing its data.
  • Database: checks that the real tables match what the extensions' install SQL expects and offers Fix.
  • Warnings and Update Sites: see below.

Updates and update sites

When an extension supports updates its manifest declares an update server: a URL to an XML file that lists the newest version. Joomla stores it in an update site. Under System > Update > Extensions you see available updates, and the control panel shows a notification. Updating an extension runs its update scripts, which may change the database, so take a backup first (see security hardening and updates).

If the Updates page says "no update sites found" for an extension, the vendor either has no update feed or you installed it without one. Then you must update manually by installing the newer ZIP over the old one.

What the manifest says

Every extension contains one XML file describing it. For a component it is named after the extension, for example com_hello.xml or hello.xml. The root element carries the type and the install method, and the child elements describe name, version, files and options. The installer reads it first and decides what to copy and where. A trimmed example:

XML
<?xml version="1.0" encoding="utf-8"?>
<extension type="module" client="site" method="upgrade">
    <name>mod_hello</name>
    <author>Ada Example</author>
    <version>1.0.0</version>
    <description>Shows a greeting.</description>
    <namespace path="src">Example\Module\Hello</namespace>
    <files>
        <folder module="mod_hello">services</folder>
        <folder>src</folder>
        <folder>tmpl</folder>
    </files>
    <config>
        <fields name="params">
            <fieldset name="basic">
                <field name="name" type="text" label="Name" default="World" />
            </fieldset>
        </fields>
    </config>
</extension>

method="upgrade" lets the same package install fresh or update an older version. The <config> block builds the settings form you see in the admin automatically.

JS Read a manifest like the installer does

Press Run (or Ctrl + Enter) to see the console output here.

No output.

This is a stand-in: the real installer also checks the Joomla version, runs SQL and script files and registers the extension in the #__extensions table.

JS Classify extensions by their prefix

Press Run (or Ctrl + Enter) to see the console output here.

No output.

A safe install routine

  1. Back up files and database.
  2. Install on a staging copy first, never straight on a live site.
  3. Read the vendor's notes for your Joomla and PHP version.
  4. Install, then open the extension's options and check the permissions tab.
  5. Test the front end, look at the error log, and only then repeat on production.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which extension type has no screen of its own and reacts to events?

    Plugins subscribe to events such as onContentPrepare and run when Joomla triggers them.
  2. 2. What does the prefix pkg_ indicate?

    A package is a ZIP of extension ZIPs installed in one step.
  3. 3. Where in Joomla 4 and later do you upload an extension ZIP?

    System > Install > Extensions has the upload, folder and URL tabs.
  4. 4. Why should you try a new extension on a staging copy first?

    Extensions run code and may alter tables, so test away from visitors and keep a backup.

Summary

  • Joomla has components, modules, plugins, templates, languages, libraries, files and packages.
  • Name prefixes (com_, mod_, plg_, tpl_, pkg_) tell you the type.
  • Install through System > Install by upload, folder or URL; plugins often need enabling.
  • The XML manifest drives installation, settings forms and updates through update sites.
  • Back up and test on staging before installing anything.

Next: Choosing and Vetting Extensions