Title: Place Order Debug Error
Last modified: June 30, 2025

---

# Place Order Debug Error

 *  Resolved [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 2 weeks ago](https://wordpress.org/support/topic/place-order-debug-error/)
 * 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!!
 * Screenshot Link : [https://drive.google.com/file/d/14skvjfcPYOOTwOF9cjfEAdCYO2PT-1OW/view?usp=drive_link](https://drive.google.com/file/d/14skvjfcPYOOTwOF9cjfEAdCYO2PT-1OW/view?usp=drive_link)

Viewing 15 replies - 1 through 15 (of 15 total)

 *  [Nagesh Pai](https://wordpress.org/support/users/nagpai/)
 * (@nagpai)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18535324)
 * 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):
 * ![](https://i0.wp.com/woocommerce.com/wp-content/uploads/2024/08/Screenshot-taken-
   on-2025-04-12-at-14.03.08-UTC%402x.png?ssl=1)
 *  Thread Starter [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18535357)
 * no debug has been turned on. It is coming like this after wocommerce 9.9.2 update
   maybe. These are the code
 * MenuDopeLookNewHowdy, adminStatusStore ActivityActivityunread activityHelpSystem
   statusToolsLogsScheduled ActionsLogsBrowse | SettingsViewing log file place-order-
   debug-153a66d7-2025-06-30DownloadDelete permanently2025-06-30T17:43:42+00:00 
   Debug [Shortcode #1] Place Order flow initiated Additional context{ “order_uid”:“
   153a66d7-55ed-4c6b-aace-4676fde8dd27”, “store_url”: “[https://www.dopelook.com.bd&#8221](https://www.dopelook.com.bd&#8221);,“
   last_error”: { “type”: 2, “message”: “session_start(): Failed to read session
   data: files (path: /var/cpanel/php/sessions/ea-php73)”, “file”: “/home/dopelook/
   public_html/wp-content/plugins/woostify-pro/modules/woocommerce/ajax-product-
   search/class-woostify-ajax-product-search.php”, “line”: 1288 }, “backtrace”: [{“
   file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-
   wc-checkout.php”, “line”: 1301, “function”: “wc_log_order_step” }, { “file”: “/
   home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-wc-ajax.
   php”, “line”: 541, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”:“-
   >” }, { “file”: “/home/dopelook/public_html/wp-includes/class-wp-hook.php”, “
   line”: 324, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-
   logging”: false}2025-06-30T17:43:42+00:00 Debug [Shortcode #2] Session updated
   with checkout data and totals calculated Additional context{ “order_uid”: “153a66d7-
   55ed-4c6b-aace-4676fde8dd27”, “store_url”: “[https://www.dopelook.com.bd&#8221](https://www.dopelook.com.bd&#8221);,“
   last_error”: { “type”: 8192, “message”: “Creation of dynamic property WC_sslcommerz::
   $msg is deprecated”, “file”: “/home/dopelook/public_html/wp-content/plugins/wc-
   sslcommerz-easycheckout/lib/sslcommerz-class.php”, “line”: 26 }, “backtrace”:[{“
   file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-
   wc-checkout.php”, “line”: 1318, “function”: “wc_log_order_step” }, { “file”: “/
   home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-wc-ajax.
   php”, “line”: 541, “function”: “process_checkout”, “class”: “WC_Checkout”, “type”:“-
   >” }, { “file”: “/home/dopelook/public_html/wp-includes/class-wp-hook.php”, “
   line”: 324, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” } ], “remote-
   logging”: false}
 *  [Nagesh Pai](https://wordpress.org/support/users/nagpai/)
 * (@nagpai)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18535418)
 * 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. 
   Prettified log contents.
   [https://pastebin.com/52e9R5wR](https://pastebin.com/52e9R5wR)
 * The log you shared indicates two issue that may be worth looking into with the
   respective theme / plugin developer.
    1. **SSLCommerz payment plugin** – Has PHP 8+ compatibility issues with deprecated
       dynamic properties.
    2. **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. 
   
   Similar thread from the past: [https://wordpress.org/support/topic/status-log-place-order-debug-error/](https://wordpress.org/support/topic/status-log-place-order-debug-error/).
   props [@lovingbro](https://wordpress.org/support/users/lovingbro/) [@mahfuzurwp](https://wordpress.org/support/users/mahfuzurwp/)
 *  Plugin Support [shahzeen(woo-hc)](https://wordpress.org/support/users/shahzeenfarooq/)
 * (@shahzeenfarooq)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18535947)
 * Hi [@dihan29](https://wordpress.org/support/users/dihan29/)
 * 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_sslcommerz`plugin
 * To assist you further, could you please try the following steps:
    1. **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.
    2. **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.
 *  Thread Starter [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536423)
 * 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.
 * MenuDopeLookNewHowdy, adminStatusStore ActivityActivityunread activityHelpSystem
   statusToolsLogsScheduled ActionsLogsBrowse | SettingsViewing log file place-order-
   debug-a39c4531-2025-07-01DownloadDelete permanently2025-07-01T08:07:00+00:00 
   Debug [Shortcode #1] Place Order flow initiated Additional context{ “order_uid”:“
   a39c4531-40d1-4980-b2d5-1d85bd284023”, “store_url”: “[https://www.dopelook.com.bd&#8221](https://www.dopelook.com.bd&#8221);,“
   backtrace”: [ { “file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/
   includes/class-wc-checkout.php”, “line”: 1301, “function”: “wc_log_order_step”},{“
   file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-
   wc-ajax.php”, “line”: 541, “function”: “process_checkout”, “class”: “WC_Checkout”,“
   type”: “->” }, { “file”: “/home/dopelook/public_html/wp-includes/class-wp-hook.
   php”, “line”: 324, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” }],“
   remote-logging”: false}2025-07-01T08:07:00+00:00 Debug [Shortcode #2] Session
   updated with checkout data and totals calculated Additional context{ “order_uid”:“
   a39c4531-40d1-4980-b2d5-1d85bd284023”, “store_url”: “[https://www.dopelook.com.bd&#8221](https://www.dopelook.com.bd&#8221);,“
   backtrace”: [ { “file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/
   includes/class-wc-checkout.php”, “line”: 1318, “function”: “wc_log_order_step”},{“
   file”: “/home/dopelook/public_html/wp-content/plugins/woocommerce/includes/class-
   wc-ajax.php”, “line”: 541, “function”: “process_checkout”, “class”: “WC_Checkout”,“
   type”: “->” }, { “file”: “/home/dopelook/public_html/wp-includes/class-wp-hook.
   php”, “line”: 324, “function”: “checkout”, “class”: “WC_AJAX”, “type”: “::” }],“
   remote-logging”: false}
 *  [Moses M. (woo-hc)](https://wordpress.org/support/users/mosesmedh/)
 * (@mosesmedh)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536618)
 * Hi [@dihan29](https://wordpress.org/support/users/dihan29/),
 * 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:
 *     ```wp-block-code
       define('WP_DEBUG', false);define('WP_DEBUG_LOG', false);
       ```
   
 * 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](https://wordpress.org/support/users/shahzeenfarooq/).
 *  Thread Starter [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536633)
 * these are already added before. But doesn’t stop it
    -  This reply was modified 11 months, 1 week ago by [dihan29](https://wordpress.org/support/users/dihan29/).
 *  Plugin Support [shahzeen(woo-hc)](https://wordpress.org/support/users/shahzeenfarooq/)
 * (@shahzeenfarooq)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536769)
 * Hi there!
   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](https://partners.woocommerce.com/English/marketplace/)
   and [Codeable.io](https://woocommerce.com/codeable/) as options for getting professional
   help. Alternatively, you can also ask your development questions in the [ WooCommerce Community Slack](https://woocommerce.com/community-slack/)
   as custom code falls outside our usual [scope of support](https://woocommerce.com/support-policy/#customization).
 *  Plugin Support [shahzeen(woo-hc)](https://wordpress.org/support/users/shahzeenfarooq/)
 * (@shahzeenfarooq)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536846)
 * Hi there!
   This is a follow-up message. Before unchecking the **“Enable logging”**
   option, please try setting the log level to any value **other than** **Debug**
   or **None**.You can find this option by going to: **WooCommerce > Status > Logs
   > Settings**.
 * 
   Let me know how that goes.
 *  Thread Starter [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18536847)
 * 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.
 *  Plugin Support [nicw.a11n](https://wordpress.org/support/users/nicw/)
 * (@nicw)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18538639)
 * Hi there,
 * 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.
 *  Thread Starter [dihan29](https://wordpress.org/support/users/dihan29/)
 * (@dihan29)
 * [11 months, 1 week ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18538789)
 * 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
 *  [Mahfuzur Rahman](https://wordpress.org/support/users/mahfuzurwp/)
 * (@mahfuzurwp)
 * [10 months, 4 weeks ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18557275)
 * Hi [@dihan29](https://wordpress.org/support/users/dihan29/),
 * Thanks for the update! We’re not able to access user websites directly, but we’re
   happy to help troubleshoot this with you.
 * Could you please share:
    - Any **fatal error logs** found under **WooCommerce → Status → Logs**
    - A **screenshot** of the error if possible
    - Whether you’ve already performed a **conflict test** by deactivating all plugins
      except WooCommerce and switching to a default theme like Storefront
    - And if you have a **staging site** where the issue can be reproduced safely
 * Looking forward to hearing from you.
 *  [Nagesh Pai](https://wordpress.org/support/users/nagpai/)
 * (@nagpai)
 * [10 months, 4 weeks ago](https://wordpress.org/support/topic/place-order-debug-error/#post-18557705)
 * The log you shared recently seems different from the one you shared earlier. 
   
   The one earlier had references to Woostify theme and SSLCommerz Payment gateway
   plugin. Are you no longer seeing those in your logs? The latest one you shared
   seems to be generated by calling `wc_log_order_step()` by very likely, some plugin
   in your system.
 *  Plugin Support [thelmachido a11n](https://wordpress.org/support/users/thelmachido/)
 * (@thelmachido)
 * [10 months, 2 weeks ago](https://wordpress.org/support/topic/place-order-debug-error/page/2/#post-18573174)
 * Hi [@dihan29](https://wordpress.org/support/users/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:
   [https://wordpress.org/support/plugin/woocommerce/reviews/](https://wordpress.org/support/plugin/woocommerce/reviews/)

Viewing 15 replies - 1 through 15 (of 15 total)

The topic ‘Place Order Debug Error’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504)
 * [WooCommerce](https://wordpress.org/plugins/woocommerce/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/)

## Tags

 * [logging](https://wordpress.org/support/topic-tag/logging/)

 * 16 replies
 * 7 participants
 * Last reply from: [thelmachido a11n](https://wordpress.org/support/users/thelmachido/)
 * Last activity: [10 months, 2 weeks ago](https://wordpress.org/support/topic/place-order-debug-error/page/2/#post-18573174)
 * Status: resolved