Support

I realized that a few websites running with Panopticon 2 and connector 1.0.7 could not get the connector updated to 1.1.0 automatically. Backend manual updating the connector works. After many different attempts, I tried to analyze the issue with AI and realized that it might be an issue in the XML file? Is that a real issue or just a problem on my side?

 

I hope this helps:

 

# Panopticon Connector update XML - targetplatform regex does not match Joomla 5.1+ or 6.x
## Summary
The Panopticon Connector's update server XML (`https://cdn.akeeba.com/updates/pkg_panopticon.xml`) uses a `targetplatform` regex that only matches Joomla 4.0–4.4 and 5.0. This prevents Joomla 5.1+ and 6.x sites from detecting connector updates through the standard Joomla update system. As a result, Panopticon cannot auto-update its own connector on managed sites running Joomla 5.1 or later.
## Environment
- **Panopticon version**: 2.0.0 (self-hosted) - **Connector installed**: 1.0.7 on most sites, 1.1.0 on a few (manually upgraded) - **Joomla versions on managed sites**: 5.2.x – 5.4.4 and 6.0.3 - **Number of affected sites**: 80+
## Problem
### 1. targetplatform regex excludes Joomla 5.1+
Every entry in `https://cdn.akeeba.com/updates/pkg_panopticon.xml` (including 1.0.8) uses:
```xml <targetplatform name="joomla" version="((4\.(0|1|2|3|4))|(5\.(0)))"/> ```
This regex matches: - Joomla 4.0, 4.1, 4.2, 4.3, 4.4 ✓ - Joomla 5.0 ✓ - Joomla 5.1, 5.2, 5.3, 5.4 ✗ **NOT matched** - Joomla 6.0, 6.1 ✗ **NOT matched**
For comparison, Akeeba Backup Professional's update XML (`pkgakeebabackuppro.xml`) correctly uses:
```xml <targetplatform name="joomla" version="((4\.(4|5))|(5\.(0|1|2|3|4|5|6|7|8|9))|(6\.(0|1)))"/> ```
### 2. The same bug exists in the GitHub source
The file `updates/pkg_panopticon.xml` in the `akeeba/panopticon-connector` repository (checked on the `main` branch) contains the same restrictive regex for ALL versions including 1.1.0. This appears to be a build template issue — the targetplatform value was never updated when Joomla 5.1+ and 6.x support was added.
### 3. CDN XML is missing version 1.1.0
The CDN file at `https://cdn.akeeba.com/updates/pkg_panopticon.xml` only lists versions up to 1.0.8. Version 1.1.0 (released 2026-03-17) is present in the GitHub repository's `updates/pkg_panopticon.xml` but has not been published to the CDN.
### 4. README contradicts release notes on supported versions
The repository README states supported Joomla versions as:
> "Joomla 4.0, 4.1, 4.2, 4.3, 4.4, or 5.0"
However, the 1.1.0 release notes state:
> "Joomla! 4.0 to 6.1, inclusive."
The targetplatform regex in `updates/pkg_panopticon.xml` matches the README (up to 5.0) but not the release notes (up to 6.1). This suggests the README and the update XML were not updated when 1.1.0 expanded Joomla version support.
For reference, the connector 1.1.0 actually installs and works correctly on Joomla 5.4.4 and 6.0.3 — we verified this on our sites. The version restriction appears to be only in the update XML and documentation, not in the code itself.
## What We Tried
1. **Verified update site is registered**: On our Joomla 5.4.4 sites, the update site `https://cdn.akeeba.com/updates/pkg_panopticon.xml` IS correctly registered in `#__update_sites`. Panopticon shows no "Update Site Missing" warning for the connector.
2. **Checked Panopticon extension update settings**: The connector is set to "Install Any Version" (which the wiki says is non-configurable and always on).
3. **Ran `site:extensions:refresh --force`**: Panopticon refreshed extensions successfully but reported "no extensions need to be updated".
4. **Ran `task:extensionupdates:director --force`**: Same result — zero extensions queued for the connector.
5. **Verified other Akeeba extensions update correctly**: Akeeba Backup Professional and Admin Tools Professional on the same sites DO detect updates through Panopticon, because their update XMLs use a correct targetplatform regex that covers Joomla 5.x.
6. **Manually fetched and compared the update XMLs**: - `pkgakeebabackuppro.xml` → targetplatform includes `5\.(0|1|2|3|4|5|6|7|8|9)` ✓ - `pkg_panopticon.xml` → targetplatform only includes `5\.(0)` ✗
## Expected Behavior
The connector's update XML should use a targetplatform regex that matches all supported Joomla versions. According to the 1.1.0 release notes, the connector supports "Joomla! 4.0 to 6.1, inclusive", so the regex should be something like:
```xml <targetplatform name="joomla" version="((4\.(0|1|2|3|4|5))|(5\.(0|1|2|3|4|5|6|7|8|9))|(6\.(0|1)))"/> ```
Additionally, version 1.1.0 should be published to the CDN at `https://cdn.akeeba.com/updates/pkg_panopticon.xml`.
## Impact
- **Panopticon 2.0 cannot auto-update its own connector** on any site running Joomla 5.1 or later — which is the vast majority of active Joomla sites today. - The wiki states the connector "always updates automatically (non-configurable)", but this is currently not possible due to the regex mismatch. - Site administrators managing 80+ sites must manually upgrade the connector on each site, which defeats the purpose of centralized management. - Panopticon 2.0 requires connector 1.1.0 for full functionality (the `/panopticon/core/update` API endpoint returns 404 with connector 1.0.7 on Joomla 5.x sites). This makes the update gap a blocker for Panopticon 2.0 adoption.
## Suggested Fix
1. Update `build/templates/update.xml` (or equivalent) to use the correct targetplatform regex matching all supported Joomla versions (4.0–6.1 per the 1.1.0 release notes). 2. Rebuild and publish `updates/pkg_panopticon.xml` to CDN with the corrected regex and including version 1.1.0. 3. Update the README to reflect the actual supported Joomla versions (currently says "4.0–5.0" while 1.1.0 release notes say "4.0–6.1").

Thank you for the fast response!

 

So do we need to mannually update the connector from the current version with the latest version, or it will be picked up by Panopticon automatically?

 

Also, do we need to disable Joomla's auto update if we are using Panopticon's Joomla Core update?

 

Thank you!

 

Thank you for the always fast and helpful update!

 

Not sure whether it is possible to make Panopticon work with the jSiteMap Pro extension's upgrade. We found that this extension always failed, and contacted their developer. However, they said that they have an update infrastructure that they cannot change now, and hopefully Panopticon could do something similar to Watchful to get them covered.

 

As this is a good SEO extension used by many sites, will it be easy to make it happen, or not?

 

Thank you and here is their reply.

 

 

Hi Barry,

actually we have an infrastructure API that has always used the email address as the license validation instead than the download key mechanism, to simplify the life to us and to clients, so this has always been the preferred approach.

I think it should be very easy for Panotpicon as it was for Watchful, to integrate it anyway.

I can provide them a free access to the extension and needed informations if this can be helpful, you can make them contact me at: [email protected]

If you enjoy my extension and support it, i would truly appreciate it if you could leave a 5-stars review. Your feedback would mean a lot and help my business grow. Let me know  and I will provide you with more details.

Thank you very much for your time!

Best regards,
John

 

On 09/04/2026 07:55, Barry Dong wrote:

Hi John,
Thank you very much for your quick response — really appreciate it!

That makes total sense. I understand that JSitemap uses a custom license validation step during the update process.

I was wondering — would it be possible for JSitemap to adopt the standard Joomla download key mechanism (the `extra_query` parameter in `#__update_sites`) for license validation? This is the approach that most other commercial extensions use (e.g., Akeeba Backup, Admin Tools, JCE Pro, SP Page Builder, etc.), and it works seamlessly with Joomla's built-in updater as well as third-party management tools like Panopticon and Watchful.

Since Panopticon is a free, open-source project maintained by a small team, it may not be feasible for them to build custom integrations for individual extensions. However, if JSitemap were to use the standard Joomla update mechanism, it would automatically work with all management tools — no special integration needed.

I believe this would also benefit JSitemap users in general, as it would simplify the update experience across the board.

Of course, I understand if there are technical reasons for the current approach. Just thought I'd raise it as a suggestion from a user perspective.

Thanks again for the great product and your support!

Best Regards,

Barry Dong

 

 

On Wed, Apr 8, 2026 at 4:04 PM Replies JExtensions Store <[email protected]> wrote:

Hi Barry,

thank you very much for your kind words about JSitemap Pro, I really appreciate it!

Regarding the issue you are experiencing with Akeeba Panopticon, it is very likely related to the fact that JSitemap uses a license validation step during the update process. Because of this, the update procedure is slightly different from standard Joomla extensions.

For this reason, external management tools such as Panopticon usually need a specific integration in order to properly handle the update workflow.

For example, the developers of Watchful implemented a dedicated integration to support JSitemap updates, allowing their system to correctly manage the license validation and the installation process.

So in this case, the best solution would be for the Panopticon developers to implement a similar integration, and I believe they might be interested in doing so if multiple users request it.

In the meantime, updating directly from the Joomla backend will continue to work correctly, as you have already noticed.

--

JPageBuilder, Build websites in minutes with Joomla's ultimate page builder: https://storejextensions.org/extensions/jpagebuilder-joomla-page-builder.html Download Free Trial

GPTranslate, the revolutionary multilanguage system for Joomla and Wordpress: https://storejextensions.org/extensions/gptranslate.html

Best regards

John Dagelmore

Joomla and Wordpress evangelist

Thanks a lot for the feedback!