Home › Forums › WoodMart support forum › PHP error in debug.log
PHP error in debug.log
- This topic has 20 replies, 4 voices, and was last updated 5 years, 1 month ago by Eric Watson.
-
AuthorPosts
-
November 5, 2019 at 11:19 am #154848
ToriTori38ParticipantHello,
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 13November 5, 2019 at 12:34 pm #154884
Artem TemosKeymasterHello,
Are you able to provide us your FTP access so we could troubleshoot it and provide you with a solution?
Regards
November 5, 2019 at 12:43 pm #154890
ToriTori38ParticipantSure 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.
November 11, 2019 at 1:24 pm #156305
ToriTori38ParticipantHello,
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
November 11, 2019 at 7:22 pm #156384
horny_fungusParticipantHave a lot of “cookie cannot be set – headers already sent” in wp-debug as well.
November 11, 2019 at 10:27 pm #156340
Artem TemosKeymasterHello,
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
November 12, 2019 at 6:31 am #156444
ToriTori38ParticipantOK we will ignore then that error if it is harmless and doesn’t effect resources. Thanks.
November 12, 2019 at 5:43 pm #156584
ToriTori38ParticipantHello,
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 13Attachments:
You must be logged in to view attached files.November 13, 2019 at 8:15 am #156665
Eric WatsonParticipantHello,
Please, provide us your FTP access so we can log in and check this on your side.
Thank you in advance.
November 13, 2019 at 9:04 am #156679
ToriTori38ParticipantHi Eric,
I have given FTP access in private content.
Thank you
November 13, 2019 at 2:19 pm #156743
Eric WatsonParticipantHello,
We found the problem and fix it in the next update.
Kind Regards
XTemos StudioNovember 13, 2019 at 2:21 pm #156745
ToriTori38ParticipantThank you again,
Can you tell me what PHP errors that will fix? There were 5 or 6 different errors.November 13, 2019 at 2:25 pm #156747
Eric WatsonParticipantAll that relate to our theme
http://prntscr.com/pwfj8vKind Regards
XTemos StudioNovember 13, 2019 at 2:28 pm #156751
ToriTori38ParticipantOK. 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.
November 13, 2019 at 3:08 pm #156766
Eric WatsonParticipantYes we checked these errors should disappear too.
Kind Regards
XTemos StudioNovember 13, 2019 at 3:43 pm #156774
ToriTori38ParticipantOK that’s great news. Thank you.
Any ETA for that update? Days or weeks?November 14, 2019 at 7:05 am #156848
Eric WatsonParticipantHello,
We plan to update in a few weeks but now we can’t say the exact date.
Kind Regards
XTemos StudioNovember 14, 2019 at 7:23 am #156855
ToriTori38ParticipantHi 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
November 14, 2019 at 7:43 am #156870
Eric WatsonParticipantThese 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 StudioNovember 14, 2019 at 7:51 am #156874
ToriTori38ParticipantYes the 500 errors and server overloading seemed to occur during editing of certain pages etc in the backend.
November 14, 2019 at 3:18 pm #156958
Eric WatsonParticipantPerhaps 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 -
AuthorPosts
- You must be logged in to create new topics. Login / Register