Bug version 2.00 2.01 2.02

Hi Patrick,

Thank you for your message.

This issue can occur if the installation was incomplete or if there was an attempt to downgrade from version 2 to version 1. Since you are receiving the message that the table joo3744_route66_metadata_backup already exists, it means the table is still present in your database. Removing this table manually should allow you to install version 2.0.2 without any problems.

Regarding the extra <span style="vertical-align: inherit;"> tags appearing in your articles, Route 66 itself does not inject any code into article content. The only exception is when using the “Continue Writing” AI tools, which insert content containing clean semantic HTML without style attributes. The tags you describe are likely caused by your text editor or another plugin.Please try deleting the table and reviewing your editor’s settings.

Let me know if you need any further assistance.

Kind regards,
Lefteris

Hi Patrick,

Thank you for the detailed information; it’s very helpful. It appears that, for some reason, Joomla has not updated the extension’s database schema version correctly, even though the database queries were executed. We’re not yet sure if this is due to a Joomla bug or another underlying cause.

We plan to release version 2.0.3 within a few hours, which should resolve this issue and allow you to update smoothly.

Best Regards,
Lefteris

Hi Patrick,

Version 2.0.3 has just been released. You can now update, and it should resolve the issue you encountered.

Thank you again for your feedback and patience.

Best regards,
Lefteris

Hi Patrick,

Route 66 does not use the onContentPrepare event in the admin. We only use onContentPrepareForm, and we do not modify the editors’ HTML. Given that, it’s unlikely Route 66 is directly injecting those <span style="vertical-align: inherit;"> tags into the editor content when you open an article.

Please try the following checks (they often reveal the culprit):

1. Disable browser extensions that modify or inspect page content (Grammarly, language/typing helpers, clipboard/formatters, HTML inspectors, accessibility extensions, certain ad-blockers or dev helper extensions).
2. Open the browser in a private/incognito window (extensions are typically disabled there) or try a different browser entirely (e.g. if you’re on Chrome try Firefox).
3. Since you said the spans don’t appear in raw HTML or in CodeMirror, that strongly points to a client-side/browser extension modifying the DOM when the WYSIWYG editor loads/saves.
    

If none of the above helps, please open a new private support ticket and include:

• A temporary admin account (create a new Super User for testing and include username/password in the ticket) or a way for me to access the site safely.
• A direct link to a specific article where the issue reproduces.

With a private ticket and admin access I’ll reproduce the issue and troubleshoot directly.

Kind regards,
Lefteris

Thanks for checking — that confirms it’s probably a browser-side extension in Chrome modifying the DOM when the editor loads. Glad to hear Firefox works as expected.

It might be worth enabling your Chrome extensions one by one until the problematic one reveals itself. Once identified, you can either disable it or replace it with an alternative.

Feel free to reach out again if anything else comes up.

Kind regards,
Lefteris

Hi Patrick,

Thank you for letting us know.

Route 66 is not affected by this attack — we do not use the format variable in any database query. In fact, format is a system (CMS) variable that simply tells the system what type of document to render.

If there were a vulnerability in handling format, it would impact any extension and even the CMS core itself, not just Route 66.

Best regards,
Lefteris