Errors in debug.log – 503's - by thisisbolo

This topic has 15 replies, 3 voices, and was last updated 6 years, 7 months ago ago by Olga Barlow

  • Avatar: thisisbolo
    thisisbolo
    Participant
    March 16, 2018 at 04:14

    Hi Olga/Rose – can you take a look at my debug.log. I’m getting quite frequent 503’s as it’s called out some of the theme files.

    Please, contact administrator
    for this information.
    14 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 16, 2018 at 13:20

    Hello,

    You provided access to themes folder on FTP so I can’t check it. I’ve installed Error Log Monitor plugin to be able to see the log in Dashboard and tried to re-save menu, theme options and page but -error log is empty.
    Here is instruction how you can enable debug mode – https://codex.wordpress.org/Debugging_in_WordPress
    Please make a screenshot once you get the 503’s so so we can take a closer look.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 16, 2018 at 13:25

    Hi Rose, debug is enabled. See content below. Can we remove screenshot?

    Please, contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 16, 2018 at 13:35

    Hello,

    The screenshot was removed.
    I do not see error messages even with the debug enabled.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 16, 2018 at 13:39

    Thank you Rose.

    I have them hidden at display in my config file. Maybe there’s something relevant in the debug.log in content folder. I’m trying to determine the root cause of the 503’s occurring. Not sure if it’s the theme or a plug-in that trips.

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 16, 2018 at 15:05

    Just following up to ensure you were able to successfully access the debug log. I’ve noticed a recurring error of ‘Trying to get property of non-object in class-wp-query.php on line 3871’

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    March 19, 2018 at 10:30

    Hello,

    To check if the problem relates to theme, you need to temporary activate a default theme on site. Also, you can disable all 3-rd party plugins, if after that the error disappears, activate plugins one by one to find out which of plugins caused the problem.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 21, 2018 at 15:49

    Hi Rose – ok, I’ll give that a shot. In the meantime I thought I’d share the following I’ve pulled out from the debug log

    Trying to get property of non-object in /wp-includes/class-wp-query.php on line 3871

    PHP Notice: Trying to get property of non-object in /wp-content/themes/xstore/framework/template-elements.php on line 1147

    post_id was called incorrectly. Product properties should not be accessed directly. Backtrace: do_action(‘wp_ajax_nopriv_et_ajax_search’), WP_Hook->do_action, WP_Hook->apply_filters, etheme_ajax_search_action, WC_Abstract_Legacy_Product->__get, wc_doing_it_wrong. This message was added in version 3.0.

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    March 22, 2018 at 12:09

    Hello,

    Check now, please.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 22, 2018 at 20:21

    Thanks Olga. On a quick look, I don’t see any bugs being logged. What is it that you did?

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    March 23, 2018 at 09:45

    Hello,

    WooCommerce made some changes and we also made improvements to the ajax search to fix the problem “post_id was called incorrectly”. This fix will be included in next theme update.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 26, 2018 at 16:20

    Hi Olga, I’ve come across more errors in debug log. Related to theme-functions.php in the framework folder and a couple others.

    [25-Mar-2018 19:29:30 UTC] PHP Notice: Undefined index: cat in /public_html/wp-content/themes/xstore/framework/theme-functions.php on line 1720
    [25-Mar-2018 19:29:30 UTC] PHP Notice: Undefined index: cat in /public_html/wp-content/themes/xstore/framework/theme-functions.php on line 1732
    [25-Mar-2018 19:29:32 UTC] PHP Notice: Undefined index: cat in /public_html/wp-content/themes/xstore/framework/theme-functions.php on line 1809
    [25-Mar-2018 20:39:40 UTC] PHP Notice: Trying to get property of non-object in /public_html/wp-includes/class-wp-query.php on line 3871
    [26-Mar-2018 14:53:44 UTC] PHP Notice: wpdb was called incorrectly. wpdb must set a database connection for use with escaping. Please see Debugging in WordPress for more information. (This message was added in version 3.6.0.) in /public_html/wp-includes/functions.php on line 4147
    [26-Mar-2018 14:53:45 UTC] PHP Warning: mysqli_real_connect(): (HY000/2002): Can’t connect to local MySQL server through socket ‘/var/lib/mysql/mysql.sock’ (2) in /public_html/wp-includes/wp-db.php on line 1531

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    March 27, 2018 at 13:33

    Hello,

    We have fixed notice with theme-functions.php. All the other notices are not related to our theme.

    Regards

    Avatar: thisisbolo
    thisisbolo
    Participant
    March 29, 2018 at 04:28

    Hi Olga, I’ve narrowed down to which plugin may be causing the other errors however, this one arose:

    First parameter must either be an object or the name of an existing class in /public_html/wp-content/themes/xstore/framework/woo.php on line 868

    I also get this error.

    [28-Mar-2018 17:04:56 UTC] PHP Notice: Trying to get property of non-object in public_html/wp-includes/class-wp-query.php on line 3871

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    March 29, 2018 at 10:28

    Hello,

    Check now.

    Regards

  • Viewing 15 results - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.Log in/Sign up

8theme customization service
We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.