Package filter in the Extensions: Manage page

[nikosdion]

Summary of Changes

Adds a Package filter in the Extensions: Manage page.

Testing Instructions

Go to System, Manage, Extensions

Actual result BEFORE applying this Pull Request

Filtering the list of extensions by the extension package ID they belong to is not possible.

Expected result AFTER applying this Pull Request

You have a Package dropdown filter. Choosing a package shows you that package extension and all extensions Joomla knows belong to that package (based on the recorded package_id in the database).

Documentation Changes Required

You need to document the Package filter:

• Package. Displays only the selected "package" type extension and all extensions which belong to it. Note: You should only uninstall the "package" type extension to prevent extension and core Joomla update problems.

Translation Changes Required

Two translation keys were added

Reasoning for this PR

It is very important that users only ever try to uninstall the "package" extension, not the individual extensions a package contains. Failing to do so will cause all sorts of problems:

• Trying to uninstall the package extension displays warnings about missing extensions which cannot be uninstalled.
• Some packages fail to uninstall because their installation scripts expect one or more of the included extensions to be present when the package uninstallation takes place.
• Removing all included extensions but not the package itself will find updates. Installing the updates reinstalls the missing extensions which can be confusing and disorienting for the user.
• Removing some of the extensions included in a package, for example some plugins, may cause the other extensions to fail in unpredictable ways.

Right now the only indication that an extension is part of a package is the meaningless Package ID column. Ask 100 users what that is for and 99 will have no idea.

Even worse, those of us who do know what it is cannot filter by a package ID, making it extremely hard to locate all extensions which belong to a package. We would have to search for the package name, note down the package ID, clear the filter, sort the list by package ID, start going through the pagination until we find the package ID in question in the rightmost column and carefully examine which extensions it contains. This is a very Soviet user experience, the only thing missing are the people in long coats asking us to please follow them to the back room for questioning.

With a filter like that it's easy to pinpoint the extensions included in a package, complete with the package itself. This makes management far easier on real world sites (default installations don't really have any packages, rendering this a moot point — but almost nobody runs Joomla like that in the real world).

[SumCompanyInc]

I have tested this item ✅ successfully on 7473cca

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37838.}

[alikon]

I have tested this item ✅ successfully on 7473cca

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37838.}

[alikon]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37838.}

[bembelimen]

Nice addition, but I will move to 4.2 and ping @roland-d to merge is asap.

[nikosdion]

@bembelimen No problem and thank you!

[roland-d]

Thanks everybody