Hello, done, i shared my credentials in the initial Hidden field.

thank you for your help Philippe

The access you have provided is not a super user access

Hello,

Thank you for contacting us, and we apologize for the inconvenience.

The issue is not coming from a core SP Page Builder addon. Based on the error and our investigation, it is being triggered by an overridden SP Page Builder addon provided by your template, as shown here: https://prnt.sc/GB1ZFRpoHwdE

Since this addon is part of the template and not developed or maintained by JoomShaper, we are unable to provide a fix for it from our side.

We kindly recommend contacting the template author and reporting the issue to them so they can update the overridden addon and ensure compatibility with the latest SP Page Builder version.

We appreciate your understanding.

Best regards

thank you for your input.

Why do you say "The issue is not coming from a core SP Page Builder addon. " ? The "articles scroll" is part of your SppageBuilder. It is an element that we choose from the Sppagebuilder left hand panel. For your info, I disabled it on the homepage, and the website is back online. "Articles scroll" addon is PART of SPPageBuilder. There is no other developer involved in this website.

Waiting for your feedback

Hello,

Thank you for your reply and for providing additional clarification.

I understand the confusion. While "Articles Scroller" does appear in the SP Page Builder addon panel and has the same name as the core addon, SP Page Builder allows addons to be overridden by templates. You can find more information about this feature here:

https://www.joomshaper.com/documentation/sp-page-builder/how-to-override-sp-builder-addons

A template developer can either:

• Override an existing SP Page Builder addon and customize its functionality.
• Create completely new custom addons that appear inside the SP Page Builder interface.

The reason I believe this issue is not coming from the core SP Page Builder addon is based on the file path shown in the screenshot I shared earlier. The addon is being loaded from your template directory rather than the SP Page Builder core directory.

If this were the original core addon, the path would be similar to:

JROOT/components/com_sppagebuilder/addons/articles_scroller

However, in your case, the files are being loaded from the template folder, which indicates that the addon has been overridden by the template.

This is also why disabling the addon resolves the issue—the overridden version is calling the deprecated method TagsHelper::getMultipleItemTags(), which is no longer available in your current Joomla environment.

Best regards

Thank you for the details. I understand much better. I'll be able to manage the issue now that I know where the problem comes from.

Best

Philippe