Hello,

Thanks for reaching out to us. 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.

Please, add screenshot of your issues.

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,

Hi, I could find a temporay fix with ChatGPT (switch off joomla debugging and error reporting) and I want to share the result, as it is possible that joomshaper can fix this, if you can reproduce the issue.

"The “bug” is most likely not in MAMP, but in the interaction between: SP Page Builder (Collections / Dynamic Content), which provides at least one value as NULL in a query or filter (e.g. an empty field, filter, sorting, or source parameter). Joomla 6 (more precisely: the Joomla Database Library), which internally calls PDO::quote() when quoting/escaping values — and PHP 8.3 raises a warning if null is passed instead of a string. Because this happens in AJAX requests when editing Collections, the response (which should be JSON) is polluted by the warning output → the SPPB UI can no longer parse the JSON and throws an error. Technically, the warning is the trigger, but the root cause is: 👉 somewhere in the SPPB Collections request, a value that should be a string is passed as NULL to the database API (or Joomla should defensively cast null to an empty string before calling PDO::quote()). Who “owns” the bug? Primarily SP Page Builder, because their Collections editor generates the problematic query/parameter. Secondarily (shared responsibility) Joomla, because the DB layer does not guard against null before calling PDO::quote() (more defensive coding would prevent this) — but Joomla cannot anticipate every incorrect parameter type coming from third-party extensions. Why disabling Debug and setting Error Reporting to “None” fixes it Because Deprecated warnings are no longer printed into the HTTP response. The AJAX response remains clean JSON, so SP Page Builder works again. What you should reasonably do now (without hacking core files) Leave it as is (Debug off, Error Reporting not set to “Maximum”) — perfectly fine for local development. If you want to report it properly: Open browser DevTools → Network → select the failing Collections request → inspect Response/Preview Collect the Joomla log and PHP error log Report it to JoomShaper with: Joomla 6.0.2, SP Page Builder 6.2.2, PHP 8.3.x; when editing Collections a Deprecated warning PDO::quote(null) is raised from the Joomla DB layer; this breaks the JSON response."

Kind regards, Matthias

Hello,

Thank you for your detailed explanation.

I will check this further. Sometimes, such issues can occur due to server configurations or template compatibility with the latest Joomla versions.

Thanks for your understanding.

Best regards,