This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Notice error that get printed as overhead

Resolved 14 replies premiumthemetheme-vantage
[email protected]
10 years ago · Last reply by Andrew Misplon 10 years ago

I get an error in Vantage that gets printed six times before the master header adding black space as overhead. It’ a notice : undefined index : panel_info in … wp-contents/plugins/siteorigin-panels/sidebar-emulator.php

How can I get rid of these messages? Or have them to get printed in a file?

URL: http://www.cumulus.qc.ca

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

14
  1. Andrew Misplon Staff 10 years, 10 months ago

    Hi Denis

    Sorry to hear about the problem.

    Please could you check for a plugin conflict. That would involve temporarily de-activating all non-SiteOrigin plugins at once. If the problem resolves, re-activate your plugins one by one, after each activation, check for the problem. When it happens again you’ll know which plugin was causing the conflict.

    (Perhaps ask your hosts if they can disable PHP notices. It would prevent this from printing on the front end).

  2. [email protected] 10 years, 10 months ago

    Hi Andrew.

    I activated .htaccess to increase memory because I had a fatal error in addition to the notice, and I added a line to stop php to display error but I still get this garbage. I was about to do what you suggest. I tried first to disable the plugins directory and it worked. Obviously I got some parts of the site not dispayed. I wanted to avoid trying every plugin because I installed quite a lot.
    Thanks.

  3. Andrew Misplon Staff 10 years, 10 months ago

    Thanks for the feedback.

    If de-activating all plugins besides Page Builder resolves the conflict them we are unfortunately dealing with a plugin conflict. I asked Greg if he had any insight what might be causing this. Besides the idea that it’s a plugin conflict he unfortunately didn’t have any further feedback.

    We unfortunately don’t know of another way to fix besides activating plugins one by one until the problem re-occurs.

  4. Andrew Misplon Staff 10 years, 10 months ago

    Well not fix, diagnose I mean.

  5. [email protected] 10 years, 10 months ago

    Ok. Done exactly that. The plugin causing the trouble is siteorigin-panels.

  6. Andrew Misplon Staff 10 years, 10 months ago

    Does the error occur if Page Builder is the only plugin activated?

  7. [email protected] 10 years, 10 months ago

    The plugin does not exist. That’s the message I get when I try to activate it. Yes I re enabled siteorigin-panels

  8. Andrew Misplon Staff 10 years, 10 months ago

    Thanks for the effort here. Sorry, I’m not quite clear on your last reply. When you re-activate Page Builder, were there any other plugins active at the time? Does the error occur if Page Builder is the only plugin activated.

  9. [email protected] 10 years, 10 months ago

    I just reinstalled and activated Page Builder. It’s the only plugin activated. The problem is still there.

  10. Andrew Misplon Staff 10 years, 10 months ago

    Super, thanks for confirming.

    Greg has hopefully resolved the problem in our development branch. If possible we’d recommend:

    * Turning off error messages and waiting until the next release of Page Builder. We’re releasing quite often at the moment.

    or

    * Delete Page Builder, download 2.0.7 here: https://wordpress.org/plugins/siteorigin-panels/developers/

  11. [email protected] 10 years, 10 months ago

    Ok. Thank you. I will try doing both. I will tell you if the problem is resolved.

  12. Andrew Misplon Staff 10 years, 10 months ago

    Thanks. For sure, let us know how this goes.

  13. [email protected] 10 years, 10 months ago

    Hi,
    I turned off error messages to my pages by creating a file named .htaccess and I wrote this script in the file :
    # supress php errors
    php_flag display_startup_errors off
    php_flag display_errors off
    php_flag html_errors off
    php_value docref_root 0
    php_value docref_ext 0

    It worked. I should have done that before.
    Next, I downloaded version 2.0.7 of PageBuilder and transferred the whole directory via ftp to the plugins directory and Voilà! Everything is now returned to normal state.
    Thank you very much, Andrew and Greg.

  14. Andrew Misplon Staff 10 years, 10 months ago

    Super, really glad this helped as a short term solution. Greg has hopefully got this resolved for Page Builder 2.1.1. When you see that particular update come up, you can then try upgrading. There will be an update suggested now, however that will just be the 2.1 update being offered.

    Thanks for your understanding and feedback.

    All the best.

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.

Have a different question or issue?

Start New Thread