Error in Debug Log

  • Resolved industrialweb

    (@industrialweb)


    4 years ago

    If I enable the Debug Log, it fills up *really* fast (thousands of copies of this line over and over again). I’ve cropped out the path to root and replaced it with “[path to root]”

    I’ve seen this exact same issue here several times, and it seems to have always been closed with no solution. I can tell you that we do not have any custom product types.

    Here is the error:

    Trying to get property ‘post_status’ of non-object in [path to root]/wp-content/plugins/facebook-for-woocommerce/includes/fbproductfeed.php on line 456

Viewing 6 replies - 1 through 6 (of 6 total)
  • B C. a11n

    (@battouly)

    Hi @industrialweb,

    Trying to get property ‘post_status’ of non-object in [path to root]/wp-content/plugins/facebook-for-woocommerce/includes/fbproductfeed.php on line 456

    This is a PHP notice, so it’s not a full-blown error. That said, it could be coming from another plugin active on the site and conflicting with the Facebook plugin too.

    Are you seeing any issues with the synchronization between your WooCommerce shop and the Facebook Catalog?

    Is this occurring repeatedly or has it just shown up a couple of times? Did it start recently while it work just fine before?

    Please share any other information which can help narrow the problem down too.

    Thread Starter industrialweb

    (@industrialweb)

    Syncing seems fine, but if I turn on debugging, it adds one of these every nanosecond and the whole debug log fills up with this – it becomes megs and megs of file in minutes. So, if ever I need to debug anything else, leaving logging enabled makes the file too large to read pretty quick. So, this plugin kills WordPress debugging for a developer. The only thing I can do is disable the plugin if I need to debug anything.

    My client installed this. Since then, they’ve been having trouble creating or editing products. I am pretty sure it is the problem. At the very least it is bogging down the server with all these error messages (and yes, I would say that trying to get a property from a non-object is an *error* happening due to a flaw).

    Hi @industrialweb,

    My client installed this. Since then, they’ve been having trouble creating or editing products.

    Since syncing is working just fine, this lets us believe there is a conflict coming from somewhere else.

    I’ve tried to replicate this on my test site, but I wasn’t able to get the result you have. I’m also not seeing reports from other users.

    Here’s how you can find out what’s the source: https://docs.woocommerce.com/document/how-to-test-for-conflicts/

    Let us know how that goes.

    We haven’t heard back from you in a while, so I’m going to mark this as resolved. If you have any further questions, you can start a new thread.

    Thread Starter industrialweb

    (@industrialweb)

    Actually, I just ended up disabling it permanently. Turning off plugins, one at a time, this was the only plugin throwing errors and the only plugin where the errors stopped when I turned it off. We’ll re-enable it for a few here or there to update our facebook feed, but leaving it on was filling up error logs like crazy.

    Hi, @industrialweb!

    Turning off plugins, one at a time, this was the only plugin throwing errors and the only plugin where the errors stopped when I turned it off.

    I totally get what you mean here. If you’d still want to give conflict testing a go, however, from the guide that was previously linked, you might want to look at the Health Check plugin if you haven’t already. That has a troubleshooting mode that automatically disables plugins and doesn’t affect how visitors view your live site. It’s a useful plugin to have, and not just for this particular issue you’re experiencing.

    • This reply was modified 3 years, 11 months ago by Cara.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error in Debug Log’ is closed to new replies.