Hello Claudio,

Thank you for reaching out to us.

This behavior is related to Joomla 6 requiring the removal of legacy compatibility plugins such as plg_behaviour_compat, which may still be depended on by installed extensions, including SP Cookie Consent.

To proceed safely, we recommend the following approach:

1. Perform the upgrade first in a staging environment (full site clone).
2. Temporarily disable System - SP Cookie Consent before starting the Joomla 6 upgrade process.
3. Ensure plg_behaviour_compat is disabled only during the upgrade phase, not on the live production site.
4. After the upgrade, reinstall or update SP Cookie Consent to a Joomla 6 compatible version.
5. Test all frontend and backend functionality before applying changes to production.

If disabling plg_behaviour_compat breaks the site, it indicates one or more extensions are still relying on legacy Joomla behavior plugins and will need to be updated before completing the upgrade.

We strongly recommend not performing this upgrade directly on production without a full backup and staging test.

Kind regards,

The problem is that I don't have a staging environment (a complete site clone) on which to test, since the site is hosted on Aruba. I haven't installed any additional plugins... just Joomla and the SPPage Builder package and its built-in extensions.

Could you please share temporary administrator access to your Joomla backend? You can provide the credentials securely in the hidden content section. Also, please take a full backup of your site before we make any changes.

Once I have access, I’ll investigate further and see what’s causing the issue. Let me know once you’ve shared the details!

Best regards,

your credentials on hidden section... thanks.

ok

You can disable the plugin here: https://prnt.sc/SNpO_M6RwUWY, then proceed with the upgrade process here: https://prnt.sc/IcUBwGQRtmXo. Once the upgrade is complete, you can re-enable the plugin.

Please make sure to take a full backup before starting the upgrade.

Thanks.

i think you mean System - SP Cookie Consent plugin...!!! i said that disable plg_behaviour_compat will crash whole site/system...

so i try to: disable System - SP Cookie Consent plugin disable plg_behaviour_compat plugin upgrade my system to joomla 6 QUESTION: once completed, have i to enable again the plg_behaviour_compat plugin??? enable System - SP Cookie Consent plugin ... is it correct??? thanks

Yes, You need to enable them again and it will not create any issues.

Thanks

Good morning, I first disabled SP cookie consent and then the backwards compatibility plugin... I updated Joomla, but first I had to manually update (as requested and reported) the Helix template... only the framework plugin had been updated... The Joomla update completed successfully and also resolved the previously reported issue (editor on custom module creation), visible in the video I recently shared on other post (43068). We now have an updated system and hope we don't encounter any further problems. Should we leave Akeeba backup installed? NOTE: The backwards compatibility plugin does NOT need to be reactivated in Joomla 6! Thank you.

Good morning,

Thank you for the detailed update.

It’s great to hear that the Joomla update completed successfully and that the editor issue on custom module creation has also been resolved after updating the Helix framework.

Regarding your question about Akeeba Backup — yes, it is generally recommended to keep Akeeba Backup installed, even after the update, as it provides a reliable safety net for future changes, updates, or migrations. You may simply ensure it is up to date and properly configured.

Also noted about the backwards compatibility plugin — you need this for SP Page Builder compatibility with Joomla 6.

Thanks again for your cooperation and for sharing the video. If any new issues appear, feel free to reach out.

Best Regards,

Ciao Claudio,

If i may join....

Are you from a European country? If yes, you have a much more restricted Cookie law than our plugin can offer. Please check/read local law regulations first. Probably extension that you have to use must REALLY block cookies, not only display messages that you have them.