Gazette 2.0.5 is Not Detected By Joomla Because Of An Incorrect Value In The JoomShaper Update XML - Question | JoomShaper

is live, now with multi-currency selling.

Gazette 2.0.5 is Not Detected By Joomla Because Of An Incorrect Value In The JoomShaper Update XML

J

Jindřich Pileček

Template 2 weeks ago

Hello,

I would like to report what appears to be an issue in the official Gazette update XML.

I currently have Gazette 2.0.4 installed on Joomla 5.4.7. Gazette 2.0.5 is available from JoomShaper, but Joomla does not offer it through the Extension Update Manager.

I investigated the update process and found a mismatch between the installed extension identifier and the identifier published in the JoomShaper update XML.

The installed Gazette template uses:

element: shaper_gazette type: template client_id: 0

Its installation manifest contains:

<name>shaper_gazette</name>

There is no separate <element> value in the installation manifest, so Joomla uses shaper_gazette as the template element.

However, the official update XML at:

https://www.joomshaper.com/updates/shaper-gazette.xml

currently publishes Gazette 2.0.5 with:

<name>shaper_gazette</name> <element>gazette</element> <version>2.0.5</version> <type>template</type> <client>site</client>

The important mismatch is therefore:

Installed extension: shaper_gazette Update XML: gazette

Joomla matches an available update to an installed extension using its extension identifiers. Because gazette does not match the installed shaper_gazette element, Joomla cannot associate the 2.0.5 update with the installed template.

The expected value in the update XML therefore appears to be:

<element>shaper_gazette</element>

rather than:

<element>gazette</element>

I also verified the installation manifests of both Gazette 2.0.4 and Gazette 2.0.5. Both use:

<name>shaper_gazette</name>

and both use the same JoomShaper update server, so the extension identifier was not renamed in version 2.0.5.

I also checked the other relevant metadata. Gazette 2.0.5 supports the Joomla 5.x range used by the site, and the update XML does not contain a PHP or database requirement that would prevent detection.

This identifier mismatch can be inspected directly in the public JoomShaper update XML and in the installation manifests of Gazette 2.0.4 and 2.0.5, independently of my Joomla server configuration.

Joomla occasionally also reports temporary update-site connection errors for several JoomShaper extensions. The relevant Gazette warning is:

Update: Could not open update site #531 "shaper_gazette", URL: https://www.joomshaper.com/updates/shaper-gazette.xml

However, the identifier mismatch described above is independently reproducible and remains present when the update XML is successfully accessible.

Could you please verify and, if appropriate, correct the <element> value in the Gazette update XML?

Thank you.

0
4 Answers
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 2 weeks ago #233886

Hi Jindřich,

Thank you very much for taking the time to investigate this in detail and for pointing out the identifier mismatch in the update XML.

We’ve checked the issue and have now corrected the <element> value in the Gazette update XML to match the installed extension identifier.

Could you please check the Joomla Extension -> Update Manager again now and let us know if Gazette 2.0.5 is being detected correctly?

We really appreciate the detailed report and your help in identifying the issue.

Best regards,

0
Toufiq
Toufiq
Accepted Answer
Senior Staff 2 weeks ago #233885

Hi there,

Thank you for reaching out, and I apologize for any inconvenience caused by this oversight. Please check again and let me know.

Best regards,

Toufiqur Rahman (Team Lead, Support)

0
J
Jindřich Pileček
Accepted Answer
2 weeks ago #233989

Hello,

thank you for fixing this issue. I can confirm that Gazette 2.0.5 is now correctly detected and displayed in the Joomla Update Manager.

Everything is working as expected now.

Thank you for the quick fix and support.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 2 weeks ago #234022

It’s great to hear that your issue has been resolved. If everything is working fine now, please mark the question as complete by accepting any of our answers.

Thank you!

0