Hi,
the SP Pagebuilder module will not save anything. I was on 3.7.15 and was getting an error message that I had exceeded allowance. I checked forums and saw it was a known error which would be fixed on latest update so I updated. Now when I try to save an existing module it wipes everything from it. If I try to import a layout and save it, it saves an empty version.
What is the problem?
Kind regards
Mel
Hi there,
Thanks for contacting us. Sorry for the inconvenience. Please update the latest version of Page Builder and check again.
-Thanks
Hi Toufiq,
apologies, I should have said that after I got that error on version 3.7.15 I found a support post that suggested upgrading to latest version. This is what I did (to 3.2) and that is when it was no loger saving anything and deletes any existing content. I would add a video to show you what happens. Even adding a new row, then selecting an addon like a header and saving doesn't work. It doesn't save the new row with addon.
Where did you added the video?
I couldn't add the video clip as there is no option on here to do so (at least that i can see)
You can share your video via google drive
Hi I have put a link to it below in hidden
Will you please provide me the Joomla administrator access to check the issue? I will check & get back to you soon.
Hi Toufiq,
apologies for the delay. I wasn't allowed to give admin access to live site but have created the same issue in a dev site based on it. Details in hidden section.
I had exactly same error message when I made a change to an SPPage builder module then I upgraded SPPagebuilder and tried editing an existing module then saved it and it cleared everything.
Once i have logged in but after some time logged out blocked the user account.
Hi Toufiq,
it is enabled again. Apologies for that I thought you had done what you needed to.
Hi,
is there any update on a fix for this as unable to create or edit new pages/content at the moment.
Kind regards
Save functionality works fine.
Hi Toufiq,
its very weird as it has also started working on live site. Maybe it was a cache issue or something and just needed for it to be cleared.
Anyway, at least it is now working.
Glad to know that your end also working :)
