Home Forums WoodMart support forum PHP error in debug.log

PHP error in debug.log

Viewing 21 posts - 1 through 21 (of 21 total)
  • Author
    Posts
  • #154848

    ToriTori38
    Participant

    Hello,

    I have the following PHP errors which are produced many many times each day in my debug.log. I need to find a fix for all of them. Can you help with any of them? My site is occassionally suffering from 500 server errors which could be down to some of these:

    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 871
    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 872
    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 873
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Array to string conversion in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: white in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 11
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: white in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: gradient in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 11
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: gradient in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13

    #154884

    Artem Temos
    Keymaster

    Hello,

    Are you able to provide us your FTP access so we could troubleshoot it and provide you with a solution?

    Regards

    #154890

    ToriTori38
    Participant

    Sure not a problem. Let me first set up a staging copy of the site so you can go in there. It might not be before tomorrow when I can do that.

    #156305

    ToriTori38
    Participant

    Hello,

    I am waiting another few days before giving you access to a staging site (both you and WPML have released updates which may have solved some of the PHP errors).

    However I have a new PHP error showing on the shop and category pages. Do you have any idea what this could be? See below. Thanks.

    Notice: wp_woocommerce_session_02480d41d944f1daa715e22d736590d2 cookie cannot be set – headers already sent by /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/header.php on line 5 in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-core-functions.php on line 892

    #156384

    horny_fungus
    Participant

    Have a lot of “cookie cannot be set – headers already sent” in wp-debug as well.

    #156340

    Artem Temos
    Keymaster

    Hello,

    This notice sometimes happens when our sessions conflict with WooCommerce ones. You can ignore these notices since they are harmless. Currently, we didn’t find a way to use WC sessions and avoid this notice.

    Kind Regards

    #156444

    ToriTori38
    Participant

    OK we will ignore then that error if it is harmless and doesn’t effect resources. Thanks.

    #156584

    ToriTori38
    Participant

    Hello,

    I have gone ahead and created a staging site for you to look at. My development domain is suffering from 500 errors whilst working in the backend, and the index.php page is having 1000’s of executions which is causing all my other sites on my hosted environment to go down. There is some issue.

    These PHP errors I showed you before are being repeatedly produced (I have listed them again below). You can also check the debug.log yourself.

    Could I please ask you to access the staging site I created (copy of live site with the issues), and see if you can help find the problem? Thanks in advance.

    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 871
    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 872
    [05-Nov-2019 07:45:46 UTC] PHP Warning: substr() expects parameter 1 to be string, array given in /home/xxxxxxx/public_html/xxxxxxx/wp-content/plugins/woocommerce/includes/wc-formatting-functions.php on line 873
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Array to string conversion in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: white in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 11
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: white in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: gradient in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 11
    [05-Nov-2019 07:45:46 UTC] PHP Notice: Undefined index: gradient in /home/xxxxxxx/public_html/xxxxxxx/wp-content/themes/woodmart/inc/integrations/visual-composer/fields/dropdown.php on line 13

    Attachments:
    You must be logged in to view attached files.
    #156665

    Eric Watson
    Participant

    Hello,

    Please, provide us your FTP access so we can log in and check this on your side.

    Thank you in advance.

    #156679

    ToriTori38
    Participant

    Hi Eric,

    I have given FTP access in private content.

    Thank you

    #156743

    Eric Watson
    Participant

    Hello,

    We found the problem and fix it in the next update.

    Kind Regards
    XTemos Studio

    #156745

    ToriTori38
    Participant

    Thank you again,
    Can you tell me what PHP errors that will fix? There were 5 or 6 different errors.

    #156747

    Eric Watson
    Participant

    All that relate to our theme
    http://prntscr.com/pwfj8v

    Kind Regards
    XTemos Studio

    #156751

    ToriTori38
    Participant

    OK. So the other errors on woocommerce/includes/wc-formatting-functions.php on line 871 / 872 / 873 – would you think they are the result of a WooCommerce problem? I need to try clear those too.

    Thank you.

    #156766

    Eric Watson
    Participant

    Yes we checked these errors should disappear too.

    Kind Regards
    XTemos Studio

    #156774

    ToriTori38
    Participant

    OK that’s great news. Thank you.
    Any ETA for that update? Days or weeks?

    #156848

    Eric Watson
    Participant

    Hello,

    We plan to update in a few weeks but now we can’t say the exact date.

    Kind Regards
    XTemos Studio

    #156855

    ToriTori38
    Participant

    Hi Eric,

    I am inclined to think it was these PHP errors which was overloading our resources and causing the occasional 500 server errors (with the index.php being accessed thousands of times as I showed you in the screenshot). Would you agree with that?

    You will have better knowledge about that than me. Thanks

    #156870

    Eric Watson
    Participant

    These errors appear only in the admin panel when editing content with some elements. They are not called on the frontend and should not load the site.

    Kind Regards
    XTemos Studio

    #156874

    ToriTori38
    Participant

    Yes the 500 errors and server overloading seemed to occur during editing of certain pages etc in the backend.

    #156958

    Eric Watson
    Participant

    Perhaps the reason is caused by these errors, we will definitely fix them in the next update. I hope this helps you.

    Kind Regards
    XTemos Studio

Viewing 21 posts - 1 through 21 (of 21 total)