Label, Search & Filter

Once you have successfully connected your installation to the Contao Manager, the Contao and PHP version will be displayed as a label. For example, if you have different versions of Contao 4.13, a default filter is also created for the minor versions. For example, you can filter all 4.13 versions with just one click. There is also a label "Manager" for all installations connected to the Contao Manager and a label "Monitoring" for all monitored installations. Furthermore, a filter for the installed packages is added.

There are two ways to add labels to an installation. One is directly when adding a new installation and the other is at any time in the detailed view of the installation.

You can also group labels. To do this, use a "colon" to separate the group and the label. For example, if you want to create a grouping for the different web hosts, proceed as follows:

Webhosting: Hostingwerk

Labels can be edited simultaneously in several installations (multiple selection). To do this, select the relevant entries by clicking on the trakked logo. Then click on the green button at the bottom of the screen and then on "Edit labels". Now you can add or delete the respective labels. To save, click on the button "Update installations".

You can change the order of the individual groups by clicking on the "cogwheel symbol" at the top right, then clicking on the six dots in front of the group name and dragging and dropping the group to the desired place.

Using the familiar Contao eye, you can hide individual groups from the "Search & Filter" list. To do this, click on the "cogwheel symbol" and then select the group to be hidden.

You can rename existing labels without creating them from scratch. To do this, first click on the "cogwheel symbol" at the top right and then edit the respective label using the "pencil symbol".

To ensure clarity in large groups, the labels automatically become a dropdown list if a group would take up too much space. To ensure that the search for labels within the dropdown is quick, an auto-complete function has also been integrated.

If necessary, you can now find your installations with a mouse click on the labels. The filters can also be combined or even reversed. Simply click twice on the label.

For example, show me all installations that "NOT" have Contao 4.13.12 installed.

By default, the "AND filter" is always used. However, if it makes sense for the label, you will see a button for the OR filter within groups. For example, you can find out which installations are trakked and generate costs. To do this, simply connect the labels "Manager" and "Monitoring" with "OR".

This makes it possible to search for specific versions of extensions or packages based on version conditions and to filter these installations accordingly. To do this, first select a package in the package filter. Then click on the "123" icon or touch and hold the label until the overlay opens to set the version condition.

Here are 3 more examples of how you can use the function.

1) Find old versions of extensions.

Let's assume you are using the extension terminal42/contao-pageimage. Currently the version 3.4.3 is installed. But there is already version 4.1.7 available. However, this is not installed, because this is not allowed by definition in composer.json.

So we would filter in trakked for the extension terminal42/contao-pageimage and additionally enter the version condition <4.0. Now trakked shows you all installations that still use an older version like 4.0. You can check these installations and change the version via the Contao Manager or directly in the composer.json.

2) Perform targeted updates

Another example would be to search for a specific version of an extension to perform selective updates.

Let's say an extension contains a bug in version 1.2.2 and an update to version 1.2.3 has been deployed. You now want to find out which installations are affected by this bug and update only those installations.

To do this, you filter for the extension in the first step and then specify the buggy version in the version condition. In our example =1.2.2.

Now you mark only these installations and let trakked do the update.

3) Find fixed versions

Sometimes it can happen that a certain version of a package has been fixed. I.e. in composer.json a specific version has been defined which is allowed to be installed. However, this prevents a newer version of a package from being installed in the future.

The problem, you forgot to document which version was fixed to and on which installations you did that. Exactly here the version constraint can help again.

In the first step, you check via the Contao Manager or Packagist which is the current version of the extension (e.g. Notification Center). As of today, this would be 1.7.2. Then you filter in trakked for the package notification_center and enter <1.7.2 for the version condition. Now you just have to check the affected installations. For this you can use the package list and look at the version condition of the composer.json.