Home>Support>Error since last update

Error since last update

By CFah, 6 years ago. Last reply by CFah, 6 years ago.
Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].

The following notice is showing on the top of a website I maintain since the last update.
Notice: Undefined index: option_name in /var/www/vhosts/95/916676/webspace/httpdocs/wp-content/plugins/siteorigin-panels/inc/sidebars-emulator.php on line 120

I tried deleting Page Builder and reinstalling it but the notice is still there.
What do I have to do to get rid of it?

Thanks for any help

Carmel

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

  1. 6 years, 9 months ago Alex S
    Hi, I Work Here

    Hi CFah,

    We’ve heard a few reports of this happening, but haven’t been able to reproduce this issue so far. Does saving the affected page resolve this issue? If not, can you try disabling all non-SiteOrigin plugins and see if this fixes the issue? You’ll need to clear all your caches after disabling your plugins.

    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.

    If you aren’t using a SiteOrigin theme, then you can also try temporarily switching to one of the default WordPress themes to see if the issue is theme related.

  2. 6 years, 9 months ago CFah

    Hi
    Thanks for your reply

    I deactivated all other plugins and cleared the cache.
    The error message did not change.
    On reactivating the other plugins the website crashed with a fatal error message.

    I am now locked out of the website and still don’t know what caused the original error.

    Have you being able to isolate what is causing the problem?

    Thanks
    Carmel

  3. 6 years, 9 months ago CFah

    Just an update.

    I have got back into the website using Filezilla and have deleted the Stripe plugin which caused the fatal error.

    I tried changing themes using Word Press twentyfifteen, sixteen and seventeen.
    The original error message is still showing on the top of the home page.
    Thanks
    Carmel

  4. 6 years, 8 months ago Alex S
    Hi, I Work Here

    Hi Carmel,

    Thank you for the additional information. Does the error message disappear upon deactivating all plugins expect SiteOrigin Page Builder?

    Have you being able to isolate what is causing the problem?

    Unfortunately, no. This is actually the third report of this type of issue occurring. We suspect the issue isn’t widespread and is due to a conflict with something specific to the affected websites – what that something is we’re not sure. Upon removing Stripe plugin having issues, were there any other results upon running the rest of the plugin conflict?

    Would it be possible for you to create a temporary admin account for us so we can log in and take a look? Also, ideally, would it be okay if we create a backup of your website for local testing?

  5. 6 years, 8 months ago Private Message - Alex S Hi, I Work Here

    This is a private message.

  6. 6 years, 8 months ago Private Message - WordPress

    This is a private message.

  7. 6 years, 8 months ago CFah

    I just noticed that the toolbar at the top is gone.
    The tabs navigating to Home, Gallery latest news etc.

    The stripe plugin is not deleted. I thought it had been but it is deactivated.
    I must have cancelled the delete without realising.

    Thanks
    Carmel

  8. 6 years, 8 months ago Alex S
    Hi, I Work Here

    Hi Carmel,

    Thanks. Would it be okay if we create a backup of your website for local testing?

  9. 6 years, 8 months ago CFah

    Yes it is ok to create a back up

  10. 6 years, 8 months ago Alex S
    Hi, I Work Here

    Hi Carmel,

    Thanks. I’ve run a few tests and I was able to resolve this issue by saving your home page. If this issue occurs again, please try saving the page to see if the error message disappears.

    Regardless of the above, It’s strongly recommended that you disable WP_DEBUG on a production site.

  11. 6 years, 8 months ago CFah

    Thanks for your help
    Carmel

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