Plugin creating huge debug.log file

  • Resolved advantagemediagroup

    (@advantagemediagroup)


    5 years, 1 month ago

    For whatever reason your plugin is filling up the WordPress debug.log file with the following error:

    “PHP Notice: id was called incorrectly. Product properties should not be accessed directly. Backtrace…”

    The debug.log file was 11GB when I checked, I simply deleted it, but it has resumed filling up again. I have just turned off the debug.log to prevent this from happening, but this isn’t ideal.

    Any idea how to prevent the error, or at the very least from it happening so much?

    Any assistance would be greatly appreciated.

    Kind regards,

    Sam
    https://thisisadvantage.com/

Viewing 1 replies (of 1 total)
  • Plugin Author PluginEver

    (@pluginever)

    Hi @advantagemediagroup,
    Sorry for the inconvenience. It is throwing a notice as it has support for the older version of WooCommerce. We will drop this support in our next update and it will solve this problem.

    BTW it is not ideal to turn on the debug log for a live site. While it is very important for the development site. Finally, thanks for sharing this with us. We will take care of it.

Viewing 1 replies (of 1 total)
  • The topic ‘Plugin creating huge debug.log file’ is closed to new replies.