The status log keeps showing a “place-order-debug” error consisting of two parts cluttering my full status log with this debug which I dont want to see. I have tried every possible way to disable this unnceccessary debug. Any way to to stop this debug which is cluttering my status log over 300times!!
Can you share a screenshot of what you see within the details of the log? Please take care to redact any private information on that.
It is likely one of your extensions – payment gateway or something related to checkout flow, has a debug setting turned on. You will need to check the settings related to them and see if there is an option to turn it off. For example, WooPayments has an option like the one in the screenshot to enable logging ( Log error messages option ) :
I took a deeper look and these are helpful debug level logs by WooCommerce indicating issues that do not hamper your site checkout, but may be a good idea to check deeper and eventually fix to prevent future issues.
The log you shared indicates two issue that may be worth looking into with the respective theme / plugin developer.
SSLCommerz payment plugin – Has PHP 8+ compatibility issues with deprecated dynamic properties.
Woostify Pro theme – The ajax product search module is triggering the session error since it is not having adequate permissions to read the sessions data.
You may want to check if these issues are causing any troubles with checkout. If not they can be taken up on a lesser priority with the respective providers.
Disclosure: I used Claude AI to summarize the logs and understand it faster.
Yes, you are right — this is expected behavior. These logs are designed to be automatically cleared if the checkout process completes successfully without any errors. They are debug-level logs, so they only appear when debug logging is enabled.
However, if an exception occurs during checkout, the log is not cleared and remains available for debugging purposes.
In the log you’ve shared, I can see one error and one warning:
1. Session Error: session_start(): Failed to read session data: files (path: /var/cpanel/php/sessions/ea-php73) File:class-woostify-ajax-product-search.php on line 1288
WooCommerce tried to start or access a session (temporary storage for checkout data), but it failed to read session data from the specified path. May be woostify plugin causes that issue
2. Deprecated Property Warning: Creation of dynamic property WC_sslcommerz::$msg is deprecated File:sslcommerz-class.php on line 26
This indicates the plugin is using outdated coding practices that are deprecated in recent PHP versions seems like appearing due to WC_sslcommerzplugin
To assist you further, could you please try the following steps:
Temporarily deactivate all plugins except WooCommerce and the payment plugin you’re using. Then, try placing a few test orders and check if any new logs are generated — and whether they disappear when the checkout succeeds.
Increase the PHP version to 8.1 or 8.2 (if supported by your host). Then check again if the session-related errors persist and whether debug logs still remain after a successful checkout.
Let us know how it goes, and we’ll be happy to assist you further.
no it is coming for everything randomly. i am using pho 8.3. Can you just let me know or any code how to disable this annoying debug so that it stops cluttering.
Thank you for getting back. I completely understand how it can feel overwhelming when logs are being generated so frequently.
As a temporary solution, you can add the following lines to your wp-config.php file. Please scroll to the end of the file and check whether these lines already exist — if they do, simply update the values to false instead of adding them again:
Keep in mind that hiding this notice doesn’t resolve the underlying issue — it’s likely a symptom of something else going on with your site. For proper troubleshooting, it’s still best to follow the conflict test steps shared earlier by @shahzeenfarooq.
Thanks for the update! Let’s try to get those error messages sorted. Could you please head over to WooCommerce > Status > Logs > Settings? Once you’re there, uncheck the “Enable logging” option. That should stop the errors from being logged. Unfortunately, there isn’t a setting to just hide specific error logs – unchecking this option will disable all error logging.
If you want to disable that specific log you need a custom code, I can recommend WooExperts and Codeable.io as options for getting professional help. Alternatively, you can also ask your development questions in the WooCommerce Community Slack as custom code falls outside our usual scope of support.
This is a follow-up message. Before unchecking the “Enable logging” option, please try setting the log level to any value other thanDebug or None. You can find this option by going to: WooCommerce > Status > Logs > Settings.
that is not the proper solution unfortunately. I kept level threshold to critical. So this shouldn’t catch this basic deprecated debug and cluttering list to over 300. Any code or fix will be helpful. I will try uncheck and see. But I am sure it will still create basic debug log which are not even critical level.
I’d just like to confirm that if you set the logging level to info in WooCommerce > Status > Logging > Settings you will not exclude default logging, but will switch off the order debug logging.
This also does not affect your server level logging, which is different from WooCommerce internal logging mechanism, and does not affect WP_DEBUG settings.
Each logger using the WC Logger gets to set it’s own logging level. If a plugin is not declaring a logging level, or uses the default level, then info is used. This is one level higher than debug which means that all logs, such as transaction logs, should continue to function normally, unless the developer has explicitly set them to below the default logging level.
No WooCommerce logging that I am aware of captures deprecation notices.
i have kept the logging off in settings. It is also throwing fatal errors from wocommerce plugin. Would be better if someone can take access of the site and check why it is happening
Hi @dihan29 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, please feel free to start a new thread.
We’d appreciate it if you could take a few moments to review the WooCommerce plugin using the link below:
