Error 0 After Trying To Reinstall SP PB 3.8.9 Following Usage Of SP PB 4.0.5 - Question | JoomShaper
Black Friday sale is live with flat 50% OFF. Sale ends soon! Grab your deal now!

Error 0 After Trying To Reinstall SP PB 3.8.9 Following Usage Of SP PB 4.0.5

GS

Guy SOUBRIER

SP Page Builder 3 years ago

Hi everybody, I faced a lot of issues using SP PB 4.0.5 and decided to reinstall SP PB 3.8.9 The reinstallation generates an error 0 on both front and backend. I switched back to SP PB 4.0.5 in order to make the site visible again. The site is running with Joomla 4.2.3, Helix Ultimate 2.0.11, php 8.1 https://www.randouveze.fr Error 0 : 1  ()  JROOT/components/com_sppagebuilder/parser/addon-parser.php:309  2  AddonParser::viewAddons()  JROOT/components/com_sppagebuilder/helpers/helper.php:95  3  SppagebuilderHelperSite::getPrettyText()  JROOT/plugins/content/sppagebuilder/sppagebuilder.php:105  4  PlgContentSppagebuilder::addFullText()  JROOT/plugins/content/sppagebuilder/sppagebuilder.php:94  5  PlgContentSppagebuilder->onContentAfterSave()  JROOT/libraries/src/Plugin/CMSPlugin.php:279  6  Joomla\CMS\Plugin\CMSPlugin->Joomla\CMS\Plugin{closure}()  JROOT/libraries/vendor/joomla/event/src/Dispatcher.php:486  7  Joomla\Event\Dispatcher->dispatch()  JROOT/libraries/src/Application/EventAware.php:107  8  Joomla\CMS\Application\WebApplication->triggerEvent()  JROOT/libraries/src/MVC/Model/AdminModel.php:1277  9  Joomla\CMS\MVC\Model\AdminModel->save()  JROOT/administrator/components/com_content/src/Model/ArticleModel.php:779  10  Joomla\Component\Content\Administrator\Model\ArticleModel->save()  JROOT/libraries/src/MVC/Controller/FormController.php:676  11  Joomla\CMS\MVC\Controller\FormController->save()  JROOT/libraries/src/MVC/Controller/BaseController.php:672  12  Joomla\CMS\MVC\Controller\BaseController->execute()  JROOT/libraries/src/Dispatcher/ComponentDispatcher.php:143  13  Joomla\CMS\Dispatcher\ComponentDispatcher->dispatch()  JROOT/libraries/src/Component/ComponentHelper.php:355  14  Joomla\CMS\Component\ComponentHelper::renderComponent()  JROOT/libraries/src/Application/AdministratorApplication.php:143  15  Joomla\CMS\Application\AdministratorApplication->dispatch()  JROOT/libraries/src/Application/AdministratorApplication.php:186  16  Joomla\CMS\Application\AdministratorApplication->doExecute()  JROOT/libraries/src/Application/CMSApplication.php:294  17  Joomla\CMS\Application\CMSApplication->execute()  JROOT/administrator/includes/app.php:61  18  require_once()  JROOT/administrator/index.php:32

I really need your help Rgds, Guy84000

0
8 Answers
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 3 years ago #89702

I have checked your site. It is running on SP Page Builder 4.0.5. Do you want me to install SP Page Builder 3 on the site?

If you want to go back to SP Page Builder 3.8.9, then you have to restore any previous backup that you have. It is not possible to revert normally by installing SP Page Builder 3 version. SP Page Builder 4 is built on a new architecture and is not reversible.

0
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 3 years ago #89541

Hello Guy SOUBRIER

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.

Best regards

0
GS
Guy SOUBRIER
Accepted Answer
3 years ago #89662

Hello Ofi Khan,

Thanks for your answer. The site https://www.randouveze.fr is running under Joomla 4.2.3, Helix Ultimate, php 8.1.

I cannot go ahead to work with SP Pagebuilder 4.0.5 mainly due to the narrow width of the text block editor which is not convenient when I have to work with large tables. Therefore I decided to come back to SP PB 3.8.9 which is much more convenient to work with.

I installed this version and the installation ran perfectly but an error 0 occurred when calling the welcome page (Accueil) on the front end.

I invite you to try the installation of SP PB 3.8.9 to see what is going on. I have a complete back up of the site just in case. By the way, is it normal that SP PB locks the data base "table xxxxx_sppagebuilder" when used? Guy84000

0
GS
Guy SOUBRIER
Accepted Answer
3 years ago #89748

Thanks for your fast answer. If we install SP PB 3.8.9, does it mean that I have to restore the site with a backup taken before I switched from SP PB 3 to SP PB 4? I'm using SP PB 4 for weeks and don't remember when I installed SP PB 4 and it would mean that I have to rewrite all the pages generated during this period. It's not feasible because the original data (photos, texts) have been erased in between. In fact my main concern working with SP PB 4 is the text block editor which is too narrow to edit easily large tables generated with JCE editor. I join a screenshot to show you my concern. Is it possible to enlarge the width of the text block editor? It would probably help a lot of your users who are facing a similar issue. https://www.randouveze.fr/images/Capture_ecran2.png Best regards

Guy84000

0
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 3 years ago #89761

Actually, there is no way to safely go back to 3.8.8 without the site backup. Anyway, the text editor issue on SP Page Builder 4 is address by the developer and will be fixed in the next release.

0
GS
Guy SOUBRIER
Accepted Answer
3 years ago #89765

Thaks for this in formation. I'll be patient until the next release. Thanks for your king assistance. Guy 84000

0
GS
Guy SOUBRIER
Accepted Answer
3 years ago #90618

Hi Ofi,

I just updated SP Pagebuilder 4.0.6 and checked the size of the window to work on tables and everything is nice now. Thanks a lot for this improvement which will ease a lot my work. Last question (for the time being): After using SP Pagebuilder, I have to unlock the data base "table xxxxx_sppagebuilder" to go ahead working easily with SP Pagebuiler. Is it normal and what could be the reason? Thanks once more to the developers… Guy84000

0
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 3 years ago #90642

You are welcome 😊

Yes, it is normal. We will improve this in the next release. Developers are aware of this.

0