Hello Ton van Loon

Please go to this location: modules/mod_sppagebuilder/fields and replace pagebuilder.php file with the attached file. You need to unzip the file and then replace.

pagebuilder.php.zip

This will fix the issue for now.

Best regards

1. I installed this, but now new SPPB Page don't render anymore on the site , especially when I open a new page and start with a row consisting of one-column, it seems to have the crash issue now on the page-component
2. Pages that don't crash, don't render properly on the site

Apology for the inconvenience. Please share your administrator access and the affected page link here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup with you before sharing.

At the moment I cannot consitently reproduce the error. I will get back to you when the issue happens again. I now use the dev-version you sent.

Okay, no problem.

I encounter the issue (crash on edit) now on an article page. Article id=268. In article edit-mode it crashed when I try to edit a text-addon.

Installed version in the modules/mod_sppagebuilder/fields folder is the dev-version of pagebuilder.php you sent me on 15-03-2022

It is not a production-site, so you can do what ever you want (just inform me a little) to investigate and test the issue. Go ahead. A cloned this site (Akeeba) from a production site where I encounter the exact same issue.

Credentials in hidden section.

Your credentials are not working. Please check and share again.

credentials changed, sorry about that

Yes, I have got the issue and shared with the developer team. Though it is not related to the module issue. It will be fixed soon. As temporary fix, use Save & Close option.

Please test all instances before the fix is released:

• SPPB in Page
• SPPB in Article
• SPPB as Module

FYI: The suggested temporary fix doesn't work, because SPPB crashes as soon as I tried to edit the add-on, not not on saving. Have you discovered the issue as I reported it?

We are checking the issue. Hopefully, it will be fixed in the next update.