Skip to content
Tutorials Center
My learning

Topics

Lesson 22 of 37 ยท Templates and Extensions

Choosing and Vetting Extensions

A practical checklist for picking Joomla extensions: compatibility, maintenance, licensing, security record, performance and a clean uninstall plan.

The Joomla Extensions Directory (JED) lists thousands of add-ons, and every one you install becomes part of your site's attack surface, speed budget and maintenance workload. Most hacked Joomla sites are not hacked through the core: they are hacked through an old third-party extension nobody remembered to update. Choosing carefully is therefore a skill worth practicing.

This lesson gives you a repeatable way to decide whether an extension deserves a place on your site, from "do I need it at all?" to "how will I remove it?". The TryIt blocks are stand-ins: a scoring tool and a small version checker, both written in JavaScript, because Joomla and the JED cannot run on this site.

Step 1: Do you need an extension?

Joomla 4 and 5 ship with a lot: multilingual support, custom fields, tags, workflows, versioning, redirects, a web service API, two-factor authentication and an updater. Before searching the directory ask three questions.

  1. Can a core feature or a setting do it? (For example, custom fields instead of a "field extension", or menu item options instead of a "hide date" plugin.)
  2. Can a few lines of CSS or a template override do it?
  3. Is the need permanent, or a one-off that a manual task would solve?

Each extension you avoid is one thing less to update, secure, learn and pay for.

flowchart TD
    A["Need a feature"] --> B{"Core setting or custom field?"}
    B -- "Yes" --> Z["Use the core feature"]
    B -- "No" --> C{"CSS or override enough?"}
    C -- "Yes" --> Z
    C -- "No" --> D["Shortlist extensions"]
    D --> E["Vet each one"]
    E --> F["Install on staging"]

Reach for an extension last, not first.

Step 2: Check compatibility

An extension must match your Joomla major version and your PHP version. Read the listing and the vendor's release notes, not just the headline. Be careful with these signs:

  • Built for Joomla 3 only. Joomla 3 reached end of life in August 2023 and receives no security fixes, so do not build new sites on Joomla 3 extensions.
  • Requires "Backward Compatibility" plugin to run. That plugin eases migration but is a bridge, not a destination.
  • Last tested on a PHP version older than the one on your server.

Joomla marks which versions an extension supports in its manifest, and the JED shows it. Always confirm with the vendor if you are in doubt.

Step 3: Check maintenance and support

An abandoned extension is a liability even if it works today. Look for:

  • A release in the last 6 to 12 months, and a changelog that mentions security fixes.
  • A public issue tracker or support forum where questions get answers.
  • Documentation, not only a demo.
  • A vendor with a track record, a real company or developer, a reachable contact.
  • Reviews on the JED that describe actual use, read the negative ones too.

Step 4: Licence, price and lock-in

Joomla extensions are usually GPL-licensed, which means you may modify them; paid ones typically sell updates and support for a period. Check what happens when the subscription ends: do you keep the extension working? Do updates stop? Also ask how your data is stored. An extension that keeps its content in its own tables with no export is harder to leave than one that saves ordinary Joomla articles or custom fields.

Step 5: Security record

Joomla maintains the Vulnerable Extensions List (VEL), where known vulnerable extensions are reported. Search it for any candidate name before you install. Also:

  • Download only from the vendor or the JED, never from "free nulled" sites; pirated copies often contain backdoors.
  • Prefer extensions that use Joomla's APIs for input, database and permissions instead of their own raw $_GET and SQL strings (the database lesson shows why).
  • After installation open the Permissions tab and give access only to the groups that need it.

Step 6: Performance and privacy

Look at what the extension loads on every page. Some install large JavaScript libraries on pages that never use them. Test on staging with the browser's developer tools: how many requests and how many kilobytes did the extension add? And check privacy: does it call third-party servers, set cookies, or send visitor data elsewhere? If you serve visitors in the EU, you may need to name those services in your privacy policy.

A scoring tool

Write the answers down; a number forces you to compare candidates fairly. This stand-in scores an extension from the checklist above. Adjust weights to what matters on your project.

JS Score an extension candidate

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

No output.

Notice the two blocking criteria: a wrong Joomla version or a known vulnerability rejects the extension whatever the other points say.

Step 7: Plan for removal

Before installing, imagine uninstalling. Does the extension remove its tables when you uninstall? Some keep data on purpose; check the documentation. Note every place you used it (modules, menu items, shortcodes in articles) so that nothing shows raw code afterwards. Disable first, watch the site for a week, then uninstall.

Keeping a version register

Keep a simple list of what is installed and its version. Comparing it with the latest versions tells you what is outdated. This stand-in compares version strings the way Joomla's updater does (numbers separated by dots, compared part by part).

JS Which extensions are outdated?

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

No output.

Note that 2.10.0 is newer than 2.9.5: comparing version strings as plain text would get this wrong, a classic bug.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What should you try first before installing an extension?

    Every extension adds maintenance and security risk, so core features come first.
  2. 2. Which source is the riskiest for downloading an extension?

    Nulled copies often contain backdoors, a common cause of hacked sites.
  3. 3. What does the Vulnerable Extensions List help you do?

    The VEL records extensions with known vulnerabilities; search it before installing.
  4. 4. Why is comparing version numbers as text a bug?

    Compare dotted versions part by part as numbers, as the updater does.

Summary

  • Prefer core features, settings, CSS or overrides over a new extension.
  • Check Joomla and PHP compatibility; avoid Joomla 3-only code.
  • Value recent releases, active support, clear licensing and a clean record on the VEL.
  • Download from the vendor or the JED only, and test performance and privacy on staging.
  • Plan the removal, and keep a version register to see what is outdated.

Next: Users, Groups and Viewing Levels