Problems With Upgrade To 4.0.0/4.0.1
Thomas Harsch
Hi,
I got a problem with upgrading frome PageBuilder Pro 3.8.7 to PageBuilder Pro V4:
My homepage is display with "missing" Pagebuilder settings (i.e. rounded edges on textblocks are not displayed anymore, the articles scroller does not work and is displayed too wide etc.). When I tried to edit a page with pagebuilder I got a white screen. After (unsupported) downgrade to 3.8.7 the page was displayed OK again. The articles looked fine so far.
Because of the problems I deinstalled PageBuilder Pro and installed the latest version which made things worse: The homepage was displayed incorrect (as described above) and now all of the articles I wrote with PB Pro are displayed in plain text. Even the button "Edit with Pagebuilder" is gone in Frontend and Backend. When I try to edit Pages created with pagebuilder, the page is shown correctly in the editor window, but when I leave the editor the site is displayed wrong.
I tried different browsers on different maschines, I tried to delete the cache in Joomla and the browsers.
Joomla version is 4.1.5, PHP 7.4.30, Debian 11, NGINX 1.18, Helix Ultimate 2.0.10 as standard template. https://picsnmore.de
Anne
Accepted AnswerHello there,
Please take our sincere apology for the experience with our product. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials.
Best regards
Thomas Harsch
Accepted AnswerHi, the problem does not persist anymore, since I restored a backup and running with Pagebuilder 3.8.8 now.
I am planning to upgrade from there and will come back to you if the problem reapears with the next attempt.
Paul Frankowski
Accepted AnswerHi Thomas,
please wait with SPPB Upgrade to at least 4.0.2 - or even 4.0.3 version. And for now personally I recommend using SPPB Pro 3.8.8 for production websites. Less worries.
Please check changelogs of components / Helix Ultimate as well.
About white page in SPPB editor, in most cases it's caused by enabled (on) JS Compression in Template Options. Yes, we informed about it in SPPB 4.x documenation, but hopefully next Helix update 2.0.11 will fix it.