Critical Issue After Updating SP Page Builder From 3.8.10 To 6.7.1 On Joomla 5.4.7 (Frontend/Backend Editor Broken & Modules Not Updating) - Question | JoomShaper

Critical Issue After Updating SP Page Builder From 3.8.10 To 6.7.1 On Joomla 5.4.7 (Frontend/Backend Editor Broken & Modules Not Updating)

FF

Franco Fadda

SP Page Builder 2 days ago

Hello JoomShaper Support Team,

I am contacting you for assistance regarding a multi-language (Italian / English) corporate website that was recently hacked and is currently being restored and upgraded on a dedicated staging environment.

Here is the summary of the steps taken and the issue I am facing:

Environment: The site was migrated from Joomla 4.4.14 to Joomla 5.4.7 Stable using the Helix Ultimate template.

SP Page Builder Upgrade:

Initially, I updated SP Page Builder Pro from v3.8.10 to v6.0.0, but the frontend editor stopped working (1054 Unknown column 'is_favorite' in 'field list').

I then performed a direct upgrade to the latest SP Page Builder Pro v6.7.1.

Current Problem:

Neither the frontend editor nor the backend pages manager are accessible (throwing PHP / SQL warnings and 500 internal server errors).

Although the main component com_sppagebuilder shows as updated to version 6.7.1, all related SP Page Builder modules remain stuck at version 3.8.10 and fail to update.

Additionally, in the SP Page Builder backend settings, only Italian is detected while English is missing, despite English (en-GB) being fully published and working properly via Joomla's native Content Languages and Language Switcher.

Could you please inspect the package update process or help realign the database structure and modules for version 6.7.1?

I can provide staging Admin credentials and FTP/cPanel access if needed.

Thank you in advance for your support!

Best regards Franco

0
11 Answers
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 2 days ago #231143

Hello Franco,

Thank you for contacting us.

The issue is most likely caused by upgrading SP Page Builder directly from v3.8.10 to v6.7.1. A direct upgrade across multiple major versions can lead to database migration issues and incomplete updates, which may result in SQL errors, 500 errors, and modules remaining on older versions.

We recommend performing the upgrade on a staging environment using the following upgrade path:

  • SP Page Builder v3.x.x → v4.x.x
  • SP Page Builder v4.x.x → v5.x.x
  • SP Page Builder v5.x.x → v6.x.x

This allows all required database migrations to be applied correctly at each major version.

Once the upgrade is completed successfully, please verify that both the component and all SP Page Builder modules are updated to the same version before proceeding.

Please try the staged upgrade process and let us know the outcome. If you still encounter any issues afterward, we'll be happy to assist you further.

Thank you.

0
FF
Franco Fadda
Accepted Answer
2 days ago #231145

Hi Ziaul, unfortunately I have versions 3.8.10, 6.00, 6.6.2, and 6.7.1. I don't have the intermediate versions and I don't see the option to download them from the dashboard.

0
FF
Franco Fadda
Accepted Answer
1 day ago #231148

Thanks Ziaul, I'll try it and let you know.

0
FF
Franco Fadda
Accepted Answer
1 day ago #231189

Hello JoomShaper Support Team,

I tried installing the first available intermediate version (v4.0.1), but the upgrade process did not complete smoothly.

After several tests, issues still persist when opening or editing pages in both the backend and frontend editors.

I have currently restored a clean copy of the production site (already updated to Joomla 4.4.14 in a separate staging/test directory. However, I need your direct assistance—preferably via backend access—to help fix the Page Builder structure.

At the client's request, my main goal is to successfully upgrade the site from Joomla 4.4.14 to Joomla 6, ensuring that both SP Page Builder and Helix Ultimate are fully updated to their latest versions without broken pages or database errors.

I am ready to provide administrator credentials for the staging environment if needed.

Thank you in advance for your help!

0
FF
Franco Fadda
Accepted Answer
1 day ago #231229

Update: I managed to update SpPageBuilder 3.8.7 → 5.3.2 on Joomla 5.4.7 :-) Now I don't know if it's better to first update the page builder from 5.3.2 to 6.7.1 and then update the core to Joomla 6.7 or vice versa

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 23 hours ago #231254

Try to install the last version of series v5.x.x then install the 6.x.x or latest one.

Thanks

0
FF
Franco Fadda
Accepted Answer
22 hours ago #231276

I tried the direct upgrade suggested by the 5.3.2 >>> 6.7.1 system, but it didn't work. I tried manually installing the package, but the site and backend stopped working. I restored the backup.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 20 hours ago #231300

If the above steps cause any issues, please update SP Page Builder gradually using the following versions:

5.3.2 → 5.7.2 → 6.2.0 → 6.5.0 → 6.6.2 → 6.7.1

Before starting each update, go to:

System → Maintenance → Database

Check whether there are any database issues. If any are found, click Update Structure to fix them before proceeding with the next update.

Thanks!

0
FF
Franco Fadda
Accepted Answer
19 hours ago #231320

The first step from 5.3.2 to 5.7.2 didn't work. I restored the backup. Error message

An error occurred. 0 Class "JoomShaper\Plugin\Content\Sppagebuilderloadmodule\Extension\Sppagebuilderloadmodule" not found

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 18 hours ago #231326

It seems that some files are missing. Please try uninstalling the application, then install it again.

Thanks!

0
FF
Franco Fadda
Accepted Answer
18 hours ago #231335

Hello, Unfortunately, I cannot uninstall and reinstall the application for two main reasons:

The error completely locks me out of the Joomla backend, making it impossible to perform any action inside the admin panel.

Uninstalling the component would risk dropping the database tables and losing all existing page layouts and content.

Every time the update fails, I am forced to restore the site from a full backup to regain control. I carefully followed the manual step-by-step package installation guidelines provided earlier.

Since this site belongs to a certified company and we are under strict deadlines, I am ready to provide temporary Super Admin and FTP credentials for this staging environment so your team can inspect and resolve the issue directly.

Thank you for your help!

0