Home>Support>Can I use different (older and actual) version of Pagebuilder due?

Can I use different (older and actual) version of Pagebuilder due?

Hi there,
I have a problem with an older version of pagebuilder. When I update to the new version it brokes my design of all sites which created by the older one. Is it possible to use both versions network wide in multisite? I know that this will be a security problem!

Thanks,

Kathrin

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 1 year, 8 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Unfortunately, it’s not possible to use two versions of the same plugin due to conflicting code.

    Can you please elaborate on the issue you’re facing upon updating SiteOrigin Page Builder? Certain older themes have issues with the new layout engine we’re using so you can use the legacy layout engine. Please navigate to WP AdminSettingsPage Builder and open the Layout tab. Set Use Legacy Layout Engine to Always and save. How does that look?

  2. 1 year, 7 months ago Kathrin

    Hi Alex,

    thanks for your soon reply! The issue is, that after update all rows are broken such the last column of the rows is shown among the rows (in the next row). For example a row with three columns before update has now two and one in the next row.

    If you think your solution will fix the issue, I will update pagebuilder again. I don’t check this before, because I have to install a backup for the hole multisite if it don’t work!

    Kathrin

  3. 1 year, 7 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Based on your description of the issue, setting Use Legacy Layout Engine to Always should resolve this issue. If that doesn’t help, do you have a public URL where we can take a look at what’s going on?

  4. 1 year, 7 months ago Kathrin

    Hi Alex again,

    Maybe you can have a look on my website quellcode (maildomain), it is one of the concering sites to estimate if your solution will realy work! That would be great!

    Thanks,

    Kathrin

  5. 1 year, 7 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Unfortunately, there’s no reliable way of knowing if using the legacy layout will help without the new layout engine being used. Your best bet would be to update and try using the legacy layout to see if that helps.

  6. 1 year, 7 months ago Kathrin

    Hi Alex,

    thanks a lot for your service and recommendation, you are a super fast and dedicated supporter!

    I will post if it works in the next days!

    Kathrin

  7. 1 year, 7 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Okay cool. Let me know how you go mate. :)

  8. 1 year, 4 months ago Kathrin

    Hi Alex,

    update an “legacy layout” didn’t work! I have unfortunately the same problem that rows with 3 columns collaps to 3 rows with 1 column and rows with 2 columns collaps to 2 rows with 1 column. Latest update 2.10.6 broke my site after changing the legacy layout from “allways” to “never”.

    It seems to be the same problem you discussed here: Thread: Legacy Layout Engine – Options failure

    The pagebuilder version which perfect design is 2.4.24 (with wigdet-bundle 1.8.1) in WP 4.8.6.!

    Please have a look at my domain (like my maildomain for login in siteorigin.com) it will be online with the latest update of pagebuilder and widget-bundle (so it will work without collaps) until tomorrow evening, before I will load my backup to repair the design for my clients.

    Thanks,

    Kathrin

  9. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    SiteOrigin Page Builder 2.5 was when the new layout engine was implemented. Based on your findings, it’s likely that your theme isn’t flexible (excuse the pun) for flex based layouts – this is quite typical of older themes. This means that you must use the Legacy Layout (which is equivalent to the pre-2.5 layout engine) for compatibility reasons. Please navigate to WP AdminSettingsPage Builder and open the Layout tab. Set Use Legacy Layout Engine to Always.

  10. 1 year, 4 months ago Kathrin

    Hi Alex,

    thanks for your fast reply, but to set the Legacy Layout Engine to “Always” don’t resolve my problem, because rows with 3 columns still collaps to 3 rows with 1 column and rows with 2 columns collaps to 2 rows with 1 column…

    Please have a short look on my site, you will see three examples in the One-Page:

    1. row with 3 columns (buttons) in 3 rows

    2. row with 2 columns (text + google-maps) in 2 rows

    3. footer with 1 row and 2 columns (impressum + contactform) in 2 rows with 1 column

    Maybe any other idea?

    Thanks a lot,

    Kathrin

  11. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    To confirm, after adjusting the Use Legacy Layout Engine to Always, did you clear your page cache and/or minify plugins? If not, please clear them.

  12. 1 year, 4 months ago Kathrin

    Hi Alex,

    this site does not use any page cache or minify plugin up to now! Which way you prefer to test (easy as possible) the compatibility between page builder and my theme?

    Thanks,

    Kathrin

  13. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Do you have a public URL where we can take a look at what’s going on?

  14. 1 year, 4 months ago Kathrin

    Hi Alex,

    yes of course I told you. But you can also click here

    Thanks,

    Kathrin

  15. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    I’ve had a look at your website and your website is still using the new layout engine. Can you please double check that Use Legacy Layout Engine is set to Always? I re-read your previous posts and you mentioned you had set it to Never. Setting Use Legacy Layout Engine to Never will force the new Layout Engine rather than disable it.

  16. 1 year, 4 months ago Kathrin

    Hi Alex,

    double checked it is definietly set to ALWAYS! I checked NEVER only to be sure what will be changed (nothing) and to inform you, that this test broke my site. I’ve understood before that it must be set to ALWAYS.

    That was not the issue yet, sorry!

    Thanks,

    Kathrin

  17. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    Thanks for confirming. Strangely, your website is still referencing the previous layout. I’m not too sure why. I can’t replicate this on any of my test sites and we haven’t received any recent reports of this happening. Hm. Do you have a server side cache? If you’re not too sure, please reach out to your hosting provider to confirm.

  18. 1 year, 4 months ago Kathrin

    Hi Alex,

    server side cache for own hosted software does not exist on my server. Page builder is aktivated networkwide in a multisite-install, maybe this can be the issue?

    Thanks,

    Kathrin

  19. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    That’s possible. Try deactivating Page Builder by SiteOrigin on the network and activating it on the specific site to see if that works.

  20. 1 year, 4 months ago Kathrin

    Hi Alex,

    deactivating page builder and widget bundle on the network and activating both only on the specific (sub)site didn’t change the result.

    But reversing this process leads to crash my site again after reactivating page builder to the network and displays the message “error” at the top left. It can also not be another plugin in conflict with page builder, because I tested first only update page builder and widget bundle and second update all plugins to the latest version without success. Both show the same result.

    I have checked the wordpress.org forum and the siteorigin forum too, if other multisite users reported problems with page builder. I found only in the siteorigin forum few users of multisite which have also problems with page builder in the latest 30 month. This all gives me the impression there is a fundamental problem between page builder and multisite since the new Legacy Layout Engine is included! Could be?

    Thanks,

    Kathrin

  21. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    I’ve run a few tests and I can’t seem to replicate this issue on a fresh Multisite install. I would try deactivating all globally activated plugins to see if any of those are conflicting.

    Typically when there are major issues, we receive a large number of reports.

  22. 1 year, 4 months ago Kathrin

    Hi Alex,

    before I wrote you today, I’ve also deactivated all other plugins in the multisite network and activated only page builder and widget bundle without success. The only one I don’t deactivated is IThemes Security, because this will produce another problems and I don’t found any conflict between page builder an ITS in google. That’s why I wrote you before that this all gives me the impression there could be a fundamental problem between page builder and multisite since the new Legacy Layout Engine is included!

    The problem for me ist not to update the design for one subsite manually, but for 5 subsites which each have between 10 to 60 pages with a wrong design too, it would be a job for one week or longer!

    Thanks,

    Kathrin

  23. 1 year, 4 months ago Kathrin

    Hi Alex,

    the next step I do is to change the theme and I will inform you about the result!

    Kathrin

  24. 1 year, 4 months ago Kathrin

    Hi Alex,

    changing the theme has also no positive effect. I tested the recommend theme thwenntyfiveteen and the lastest update of my theme sydney.

    I have discovered a mistake (by using latest page builder and widget bundle) that may give an indication of the cause. In the pages or posts you can usually choose between visual, text or page builder, but the option page builder is missing in the choices, so I could not edit even existing pages that were created with page builder, subsequently.

    Thanks,

    Kathrin

  25. 1 year, 4 months ago Kathrin

    Hi Alex,

    addendum to the last comment: In the settings of page builder, I have of course choosen the option that page builder is activated in pages and posts! Nevertheless, the option page builder in pages and posts is missing.

    Thanks,

    Kathrin

  26. 1 year, 4 months ago Kathrin

    Hi Alex,

    my site is still online with the latest versions of page builder and widget bundle so you can find the bug!

    Thanks a lot for your support,

    Kathrin

  27. 1 year, 4 months ago Alex S Hi, I Work Here

    Hi Kathrin,

    I’m sorry to hear that. Unfortunately, we’ve been unable to replicate this issue. I’ll log this issue with the development team and they’ll see if they can find anything. It’s not ideal, but you should consider reverting back to the previous version of SiteOrigin Page Builder where you weren’t experincing issues.

  28. 9 days, 2 hours ago Kathrin

    Hi Alex and Siteorigin-Team,

    up to now I followed the idea from Alex (1 year 3 month ago) and revert back to the previous version of SiteOrigin page builder 2.4.24 (with wigdet-bundle 1.8.1 in WP 4.8.6) to have not described issues. In the meantime I updated several versions of page builder + widget bundle which didn’t solve the problem for me and a lot of sites in a multisite install.

    But now I must update to wordpress 5.5 and I think page builder 2.4.24 is not compatible with 5.5. That means I won’t be able to edit old content from page builder 2.4.24 even if I use the classic editor plugin, right?

    What can I do?

    Thanks,
    Kathrin

  29. 8 days, 12 hours ago Alex S Hi, I Work Here

    Hi Kathrin,

    I’m sorry to hear you’re still facing this issue. Can you please try installing Enable jQuery Migrate Helper to see if that helps?

    Kind regards,
    Alex

  30. 8 days, 7 hours ago Kathrin

    Hi Alex,

    I red in the support forum to this plugin a lot of new problems when activated in multisite. Before I will install and test it, what do you think about which problems will produce a migration in blocks? Your team made surely some tests for compartibility between page builder and the new wp block editor.

    Thank you so much for your help,

    Kathrin

  31. 8 days, 6 hours ago Andrew Misplon Hi, I Work Here

    Hi Kathrin

    At the moment, we don’t have any open issues logged for multi-site installs. We use Page Builder in our own multi-site install without issue.

    Page Builder pages will remain in the Classic Editor format without the use of the Classic Editor plugin although using the Classic Editor plugin makes maintaining the same format for all pages simpler. If you want to migrate classic Page Builder pages to the SiteOrigin Layout Block in the Block Editor, the migration will need to be done on a per-page basis, manually.

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More