No pagebuilder available after update

Hi Sparen

Thanks for reaching out. Is a working baseline available? Does Page Builder work with a default theme like Twenty Twenty activated and all plugins deactivated except for Page Builder?

Hi Andrew,

as I wrote “All plugins were deactiveted step by step and theme changed but pagebuilder is not available in the backend again!”

TwentyFifteen and TwentiTweniTwo tested with no positive result – no working baseline available up to now!

Thanks,
Sparen

Hi Sparen

We’re discussing different methods. It’s possible to get different results with a step-by-step deactivation. It’s only necessary to reactivate plugins one by one if a working baseline is found. If no working can be found, then the test has failed.

To confirm, did you test Page Builder with no other plugins activated? It’s not clear if that was done.

Hi Andrew,

I confirm all plugins were deactivated, except IThemes-Security, for understandable reasons!

Thanks,
Sparen

Hi Sparen

Thanks for the update.

It should be ok to deactivate your security plugin for a minute.

When the issue occurs, please, try checking for JS errors:

https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis

Hi Andrew,

I found some errors using the browser console:

1. GET …/plugins/siteorigin-panels/css/admin.min.css?ver=2.19.0 – 404 not found
2. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.19.0 – 404 not found
3. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.19.0 – 404 not found

The issue should be that I always rename the plugin folders to reduce hacker attacks to known plugin names and Url’s! The folder “siteorigin-panels” was always renamed to “builder” up to now.

In the past it worked very well to rename the plugin foulder, but could it be that Siteorigin now forced to load scripts only from the original plugin name foulder?

Thanks,
Sparen

Hi Sparen,

I’ve run a few tests and I was able to rename the siteorigin-panels directory to just builder while using 2.22.0 and have everything work as expected (Page Builder appeared and worked, no 404’s or references to the siteorigin-panels directory). We haven’t modified how the assets listed are loaded. They’re set to be dynamically loaded based on the directory loading the files rather than siteorigin-panels.

How are you renaming the siteorigin-panels directory? Are you renaming it directly (using a file manager or FTP), or with the help of a third-party plugin?

I recommend reinstalling the plugin to see if that helps. You can do this by navigating to Plugins > Installed Plugins and deactivate Page Builder by SiteOrigin, and then delete it. Scroll to the top of the page and click Add New and search for Page Builder by SiteOrigin. Once found, install it. Rename the Page Builder directory as you normally would and then activate Page Builder.

Kind regards,
Alex

Hi Alex,

I renaming the plugin directly by FTP!

To be sure that the issue doesn’t depend on update from the wordpress-backend, I delete 2.19.0 by FTP, download the current release 2.20.0 manually, rename locally on PC and upload the renamed plugin by FTP. After activation I get the same errors as before using the browser console:

1. GET …/plugins/siteorigin-panels/css/admin.min.css?ver=2.20.0 – 404 not found
2. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.20.0 – 404 not found
3. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.20.0 – 404 not found`

Why css and javascript files will load from the plugin “siteorigin-panels” if there are no plugin with this name exists (only “builder”) and you haven’t modified how the assets are loaded?

Thanks,
Sparen

Addition:

Security-Plugin deactivted (the last one active of all plugins) also deactivated (Andrew) but no positive result!

No caching problem, all ohter renamed plugins work very well. It seems to be a php 8.0 issue, but which one?

Thanks in advance,
Sparen

Addition:

If I want to add a block with sitorogin layouts to a page, I get another error in browser console:

ReferenceError: panels is not defined react-dom.min.js:9:64017
…/plugins/builder/compat/js/siteorigin-panels-layout-block.min.js?ver=2.20.0:1

As you can see before the renamed plugin name “builder” is found, but css and javascript still load from the original plugin name folder “siteorigin-panels”:

1. GET …/plugins/siteorigin-panels/css/admin.min.css?ver=2.20.0 – 404 not found
2. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.20.0 – 404 not found
3. GET …/plugins/siteorigin-panels/js/siteorigin-panels.min.js?ver=2.20.0 – 404 not found
4. GET …/plugins/siteorigin-panels/js/styling.min.js?ver=2.20.0 – 404 not found

For me it looks like that any modification must exists that the assets (1./2./3./4.) have to load from the original plugin name folder “siteorigin-panels”!

Thanks,
Sparen

Hi Sparen,

Thank you for the additional information. With your help, I’ve identified a situation where Page Builder won’t allow for the non-standard directory name and submitted a patch to account for this situation. This change should be available in an upcoming release.

Kind regards,
Alex

Hi Alex,

nice to hear that you found the issue and will fix it in the upcoming release, because I was forced to put all websites using page builder in coming soon mode since two weeks.

Please wait to mark this thread as resolved until I could test the upcoming release!

Thanks a lot and best regards,

Sparen

Hi sparen,

I’ve prepared a patched version of Page Builder that includes the fix I mentioned. This will allow you to test it and resolve this issue prior to the next Page Builder update. You can download it by clicking here.

Before proceeding, do a backup.

Navigate to Plugins > Installed Plugins and deactivate Page Builder by SiteOrigin. Delete it and then scroll to the top of the page and click Add New, Upload Plugin. Upload siteorigin-panels.2.20.1-beta.zip and when prompted activate it.

Kind regards,
Alex

Hi Alex,

thanks a lot for the beta of the upcoming release. I have tested and it is now working well on the main page (all assets of the plugin are loaded now from the renamed plugin folder “builder”).

However a small problem still exists if you run a multisite inviroment like me. Browser console tells me 3 errors in subsites with the same issue:

1. the cross-origin or cross-site access is missing (CORS-header ‘Access-Control-Allow-Origin’).

https://developer.mozilla.org/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin?utm_source=devtools&utm_medium=firefox-cors-errors&utm_campaign=default

2. downloadable font: download failed (font-family: “siteorigin-panels-icons” style:normal weight:400 stretch:100 src index:1): bad URI or cross-site access not allowed source: https:…/plugins/builder/css/icons/panels-icons.woff2?

3. GET …/uploads/sites/5/2017/02/……550×400.jpg – 404 not found

Pleas fix it for the upcoming release and if you have enough time I would be very grateful to get a new beta ealier!

Many thanks and best regards,

Sparen

Hi Sparen,

It’s great to hear that helped! The update we just released included the changes in the provided beta to allow for this so you can safely update to the latest version.

1. A CORS error is a sign that your website isn’t setup to allow for requests across domains (www and non-www is considered cross-domain). I recommend reaching out to your hosting provider about this as it’s not a Page Builder issue.

2. This is occurring because of 1.

3. This is unrelated to Page Builder. I recommend ensuring re-adding the missing image on your website or removing references to it.

I’ve marked this thread as resolved as the original issue has been resolved and has now been released.

Kind regards,
Alex