Issues Encountered with SP PageBuilder Version 5.0.6
Dear Joomshaper Team,
First and foremost, I would like to extend my gratitude for addressing the issues I highlighted in my previous ticket. I'm pleased to note that installing version 5 of SP PageBuilder no longer disrupts the layout of existing pages. With this positive change, I was eager to test the new version further.
However, while using it, I've encountered several concerns that I hope can be addressed:
-
Saving Requirements in Backend:
When using SP PageBuilder in the context of Joomla articles (backend), it is mandatory to save the page before accessing PageBuilder. After finalizing the content within PageBuilder, I need to save the file both in PageBuilder and in Joomla. This dual-saving process is quite confusing and counter-intuitive. -
Issue with Pre-generated Code:
A significant part of my website relies on code that's pre-generated by my database. While I can introduce this code into PageBuilder and even preview it without any hitch, the main problem arises after saving. The Text add-ons used to introduce the HTML code appear blank, resulting in an empty output on the final page. This is a major issue for me, especially since almost 30% of my site consists of this pre-generated code. It's worth noting that I never faced this issue with version 3. -
Column Resizing Limitation:
A minor but noticeable issue is the inability to resize columns within SP PageBuilder. The central column, used primarily for layout, is disproportionately large, leaving a very narrow column on the right for text or code input. This restricts the workspace and makes the design process cumbersome.
In light of these challenges, I found it necessary to revert to version 3. I genuinely hope to see these issues addressed in future releases, making SP PageBuilder even more efficient and user-friendly.
Looking forward to a more refined version soon.
Warm regards,
Jean-Marie Putz
You can adjust the tone and specific details as per your preference before sending it.






