Hi Wayne,

Thanks for reaching out to us.

Could you please confirm which SP Page Builder version you're currently using? Also, please share a screenshot of the error message you're seeing during the installation.

That will help us investigate the issue more accurately.

Thanks

Hi, after updating SP Page Builder 3.7.12 to SP Page Builder 5.6.1, a message appears on the homepage of the website:

Fatal error: Declaration of JoomShaper\SPPageBuilder\DynamicContent\Model::offsetExists(JoomShaper\SPPageBuilder\DynamicContent\mixed $offset): bool must be compatible with ArrayAccess::offsetExists($offset) in /web/htdocs6/veichicz/home/www/administrator/components/com_sppagebuilder/dynamic-content/Model.php on line 419

I want to install the SP Page Builder Security Patch v1.0.1, which can only be installed on SP Page Builder 5.6.1. I tried this procedure on my first website, but I prefer not to continue. I still have 4 more websites with versions: SP Page Builder 3.1.2, SP Page Builder 2.3.4, SP Page Builder 3.8.7, SP Page Builder 3.0.4

How do I continue?

Dalibor

Hi Dalibor,

Since your websites are running very old versions of SP Page Builder, we do not recommend upgrading directly to v5.6.1. Instead, please upgrade step by step using the following sequence:

• v3.8.10 (latest v3 release)
• v4.0.1
• v4.0.11
• v5.0.0
• v5.0.10
• v5.1.0
• v5.1.9
• v5.2.9
• v5.5.0
• v5.6.1

As your sites are using some of the earliest SP Page Builder versions, following this upgrade path will help ensure a smoother and safer migration to the latest version.

You can download the older releases here:

• https://www.joomshaper.com/downloads/extension/sp-page-builder-pro-next

You can also download the latest v3 release (v3.8.10) from:

• https://www.joomshaper.com/downloads/extension/sp-page-builder-pro

Additionally, please follow the instructions provided in this forum post:

• https://www.joomshaper.com/forum/question/46032

Thanks!

Hello,

The dynamic content issues are occurring because you previously installed SP Page Builder 5.6.1 and have now downgraded to an earlier version. This can leave behind data or files that are incompatible with the older version.

To resolve the issue, you will need to manually uninstall SP Page Builder and then follow the recommended upgrade steps from previous respond.

As mentioned previously, the original post is private, so I'm pasting our Team Lead's response here for your reference:

Recommended Update Versions SP Page Builder Pro: 4.0.7 → 4.0.11 → 5.7.2 → Latest SP Page Builder 6 version Helix Ultimate Framework: 2.0.11 → 2.2.9 Travelin Template: 1.0.2 → 1.0.5

Note: If you are using Joomla 3 and only need to apply the security fix, please use the dedicated Joomla 3 security patch: https://www.joomshaper.com/downloads/extension/sp-page-builder-joomla-3-security-patch

Since these are major version updates, we recommend backing up your custom CSS, template overrides, and other customizations before proceeding.

1. Updating SP Page Builder from 4.0.7 Since you are currently using SP Page Builder 4.0.7, we recommend updating it in stages rather than updating directly to the latest version.

Recommended update path:

SP Page Builder 4.0.7 → 4.0.11 → 5.7.2 → Latest SP Page Builder 6 version

If your website is still running Joomla 3 and your primary concern is the security issue, please use the following security patch:

https://www.joomshaper.com/downloads/extension/sp-page-builder-joomla-3-security-patch

2. Recommended Update Order We recommend performing the updates on your staging site first.

Recommended order:

Helix Ultimate Framework SP Page Builder Travelin Template After each update, check both the front end and administrator area to make sure everything is working correctly before proceeding to the next update.

3. Menu Issues After the Update If you experience any menu-related issues after updating Helix Ultimate, please follow the instructions in this video:

https://drive.google.com/file/u/2/d/1v2R-eARoKrr73OvFMMVA0E3IVdAN7ReM/view

4. Backup and Best Practices Before starting the update process, make sure you have a complete backup of your staging site, including both the files and database.

We also recommend keeping separate backups of:

Template settings SP Page Builder pages Custom CSS Template overrides Other customizations If you are using custom JavaScript, make sure the code is fully functional and does not conflict with the core files or functionality of the template, Helix Ultimate, or SP Page Builder.

Since you already have a staging environment, we strongly recommend completing the entire update process there first.

Thoroughly check your pages, menus, responsive layouts, custom CSS, overrides, and other functionality. Once everything is working correctly on staging, you can follow the same process on the production website.

Best regards,

Toufiqur Rahman (Team Lead, Support)

WHAT AN ABSOULTE DUMPSTeR FIRE.. IM SiMPLY Going TO CUT THe THREe Clients WEBSITES LOOSE ANd risk LOSING THEIR BUSINESS..after a Stroke last year related to stress, this is too much

yall have definitley lost mine business and my interest in any website devEliping fOR 20 years in the business..im going into lawn care and flower arranging.. GOODBYE