Support » Plugin: Page Builder by SiteOrigin » Trash after update

  • Seit dem heutigen Update funktioniert der Pagebuilder nicht mehr, man kann kein Widget bearbeitet abspeichern.

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Support alexgso

    (@alexgso)

    Hi @andrebraselmann,

    From the sounds of things, this might be a plugin conflict. Would you mind running a quick plugin conflict test?

    You can start by disabling all non-SiteOrigin plugins and see if this fixes the issue. You’ll need to clear all your caches after disabling your plugins. So just to confirm, double check if the issue is coming up while all other plugins are disabled.

    If it does fix the issue, then try re-enabling your plugins one by one until the issue comes back. This procedure will help diagnose which plugin is causing the issue. Once we know that, we’ll be able to look at what might be causing the conflict and either solve the problem or help you find an alternative plugin.

    You could also try temporarily switching to a default WordPress theme like Twenty Sixteen. Default WordPress themes are generally very light weight which lowers the chance that they’ll conflict with plugins, so they’re a good way to test if your original theme is the source of the issue.

    Hi Alex,

    i disabled all SiteOrigin Plugins, clear the cache, then i enable the pagebuilder plugin allown, but the same issue. When i click on ready, nothing were saved.

    Plugin Support alexgso

    (@alexgso)

    Hi andrebraselmann,

    To confirm, did you disable all SiteOrigin plugins or all non-SiteOrigin plugins (as in, all plugins but our plugins)?

    Also, does this issue occur on all pages or just one specific page?

    I disable all plugins which have sonething to do with the pagebuilder. This troubleshooting were on all my 6 websites where i’m using the siteorigin pagebuilder.

    Plugin Support alexgso

    (@alexgso)

    Hi andrebraselmann,

    Thanks for clarifying. Unfortunately, that’s an incomplete plugin test. You need to disable all plugins but SiteOrigin Plugins. To make things easier, you should only have the following two plugins active:

    Page Builder by SiteOrigin
    SiteOrigin Widgets Bundle (if you have it installed)

    All other plugins need to be disabled for the plugin conflict test to work.

    Please wait a moment, i think its not the plugin, it will be the the theme.

    Nothing, only on 1 site, where i have the pagebuilder since 3 weeks, the plugin ist running perfect, but the editor looks like the old version.

    https://www.abrama.de/wp-content/uploads/2017/12/Ashampoo_Snap_2017.12.19_09h18m11s_002_Seite-bearbeiten-André-Braselmann-abrama-WordPress-Mozilla-Firefox.png

    On my new site, where i’m installing your pagebuilder, the plugin doesn’t running, an its look like the new version.

    https://www.abrama.de/wp-content/uploads/2017/12/Ashampoo_Snap_2017.12.19_09h17m14s_001_Seite-bearbeiten-Mein-Schlauchmagen-WordPress-Mozilla-Firefox.png

    Plugin Support alexgso

    (@alexgso)

    Hi andrebraselmann,

    The first screenshot is correct, and the second screenshot isn’t correct. We haven’t changed the interface so I’m unsure what is happening with the second site.

    What version of SiteOrigin page Builder is used on the second website? Can you please send me a screenshot of the plugin listed in the plugins list?

    I see it, on the first is running version 2.6.0, and on the second 3.0.0

    Plugin Author Andrew Misplon

    (@misplon)

    Hi @andrebraselmann. Sorry this reply was missed, it wasn’t intentional. Page Builder by SiteOrigin hasn’t yet reached version 3.0.0 yet. We’re currently on 2.6.2: https://wordpress.org/plugins/siteorigin-panels/. If the version number is 3.0.0 then you’re most likely using a forked version in that installation. In that event, it would be best to reach out to the developers that forked Page Builder.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Trash after update’ is closed to new replies.