Summary
After upgrading Joomla to 6.1.2 ("Nyota") and PHP to 8.3.31, the SP Page Builder Pro backend page editor and the frontend editor's save action both fail with the same fatal error: "Call to a member function getTable() on false". Updating SP Page Builder Pro from 6.6.0 to 6.7.0 did not resolve the issue.
Environment
CMS: Joomla 6.1.2 "Nyota" (upgraded from 5.4.5)
PHP: 8.3.31 (upgraded from 8.2)
SP Page Builder Pro: 6.7.0 (updated from 6.6.0 — issue present in both versions)
Template: Delacroy (JoomShaper), Helix Ultimate 2.2.6
Hosting: loswebos.de (host01.loswebos.de)
Issue 1: Backend page editor fatal error
Steps to reproduce:
Log into the Joomla administrator panel.
Go to Components → SP Page Builder → Pages.
Click on any page title to open it in the backend editor (URL pattern: index.php?option=com_sppagebuilder&task=page.edit&id=X).
Result:
A fatal error page is shown instead of the editor:
Es ist ein Fehler aufgetreten.
0 Call to a member function getTable() on false
This happens for every page tested (tried with multiple page IDs), not just one specific page — so it appears to be a general incompatibility rather than a corrupted single record.
Issue 2: Frontend editor save fails with the same error
Steps to reproduce:
Open a page from the frontend using the Frontend Editor link (e.g. index.php/<menu-alias>/edit/<id>).
The frontend editor loads correctly and content can be edited.
Click "Save".
Result:
The Save button spins indefinitely. Browser console shows:
Uncaught (in promise) SyntaxError: Unexpected token '<', "<html><hea"... is not valid JSON
This indicates the save AJAX request is receiving an HTML fatal-error page back from the server (the same "Call to a member function getTable() on false" error) instead of the expected JSON response, so no changes are persisted.
Additional notes
-
Enabling Joomla's "System Debug" and setting Error Reporting to "Maximum" (Global Configuration) did not produce a more detailed stack trace — the error is shown as a generic message in both cases, suggesting it may be a PHP Error/TypeError (PHP 8+ behavior when calling a method on false) that bypasses Joomla's normal exception/debug output.
-
We suspect a Joomla 6 core API change (a method or class SP Page Builder relies on for getTable() may have been removed, renamed, or now returns false under different conditions in Joomla 6 vs. Joomla 5).
-
This is currently blocking all content edits to existing SP Page Builder pages on the site, both via backend and frontend editing.
Request
Could you confirm whether SP Page Builder Pro 6.7.0 is expected to be compatible with Joomla 6.1.2, and if not, provide a timeline or interim fix? Happy to provide further details (full URL, temporary admin access, or server error logs) if helpful for debugging.
