My problem is the Sitemap, if I try to view it without Login in Frontend I get this error:
This page contains the following errors:error on line 70 at column 8: Opening and ending tag mismatch: input line 66 and formBelow is a rendering of the page up to the first error.
While if I log in I get this error:
This page contains the following errors:
error on line 29 at column 90: Opening and ending tag mismatch: input line 29 and divBelow is a rendering of the page up to the first error.
I tried to solve the problem by reading the various tickets and checked what was recommended, then I tried to send the address https://camminateinfriuli.it/index.php/component/route66/sitemapindex/1?format=xml as a Sitemap to Google
and I get the following error from Google:
Sitemap
/index.php/component/route66/sitemapindex/1?format=xmlLast read 11/05/25 Pages detected 0 Videos detected0
The Sitemap can be read, but has errorsUnsupported file format1 instanceIt seems that your Sitemap is not in a supported format. Verify that it complies with our Sitemap Guidelines and resend it.
Why or how can I solve it?GreetingsGianni
#1350
Posted in ‘Route 66’
Sitemap Problem
Latest post by Lefteris Kavadas on Saturday, 14 June 2025 18:37 EEST
Sunday, 11 May 2025 13:39 EEST
Camminateinfriuli
Monday, 12 May 2025 13:38 EEST
Lefteris Kavadas
Hi Gianni,
Thank you for your message.
I’ve checked your website and noticed that you’re using Akeeba Engage. It appears that this extension is injecting the login form across all pages, including your XML sitemaps.
If you’re not actively using Akeeba Engage, I recommend disabling or uninstalling it. If you are using it, please ensure that it’s updated to the latest version. Should the issue persist after updating, I suggest reaching out directly to the developers of Akeeba Engage to report the problem, as they’ll be in the best position to assist.
Let me know if you need any help with this process.
Best regards,
Lefteris
Saturday, 14 June 2025 11:43 EEST
Camminateinfriuli
I did some research—it's not Akeeba Engage that's causing the issue, but the System – Login Modal plugin. Everyone who enables this plugin encounters the same error. Perhaps you could fix it or collaborate with the Joomla developers to resolve it.
Saturday, 14 June 2025 18:37 EEST
Lefteris Kavadas
Hi Gianni,
Thank you for the follow-up and for taking the time to investigate further.
When I initially checked your site back in May, it appeared that Akeeba Engage was responsible for injecting the login form. However, it’s entirely possible that they have since released an update that resolved the issue.
Regarding the “System – Login Modal” plugin, I appreciate you pointing that out. I wasn’t previously aware that it could cause this behavior. Unfortunately, since the issue stems from that plugin injecting HTML into pages where it shouldn’t—such as XML sitemaps—there’s nothing we can change on our end to prevent it. Our extension simply outputs valid XML markup, and their plugin is introducing unexpected content.
That said, I’d be happy to collaborate or share technical details with the developers of the plugin to help resolve this. It’s definitely in everyone’s interest to ensure compatibility.
Let me know if you’d like me to reach out to them or if there’s anything else I can help with.
Best regards
Lefteris
Note: An active subscription is required in order to get support for our paid extensions. For our free extensions, if you don't have an account, register and then submit your support request. In case you just want to ask a question, you can also use the contact form .
