Hi again @markovsites thank you for updating the logs. The logs suggest that the error lies in a file called TestCheckout.php. WooCommerce has no such file by that name in its file structure.
So its an error coming from a different plugin. To diagnose further, please update us with the System Status Report on WooCommerce -> Status.
Thanks,
Jim
-
This reply was modified 6 months, 2 weeks ago by
James Kiarie.
hi @mosesmedh @jamesgreat
Just to let you know, I have already fixed the WP_DEBUG issue in the wp-config.php file (it was defined twice).
So that should no longer cause any confusion or distract from the main checkout problem.
https://pastebin.com/qQUSixSb
Hi @markovsites,
Thank you for the update, it is great to hear that the WP_DEBUG duplication has been cleaned up, that helps keep the focus on what is affecting the checkout issue itself.
From the System Status Report you shared, nothing concerning stood out. WooCommerce is installed correctly and the checkout page is set with the standard WooCommerce shortcode woocommerce_checkout. This usually indicates that the core setup is fine, and the issue is likely coming from the file mentioned in your logs, TestCheckout.php. Since WooCommerce does not include such a file, it is very helpful to confirm whether this file exists anywhere in your site files, as it may be what is interfering with the checkout page loading.
Please check your hosting file manager or connect through FTP and search for TestCheckout.php. You can look inside wp-content, then inside plugins or mu-plugins, or even your active theme folder. If you find it, remove the file or temporarily rename it to something like TestCheckout-disabled.php, then test the checkout page again.
Let us know what you find and how the checkout behaves after removing or renaming that file, and we will move forward from there.
Hi @lovingbro Thank you, but I cannot find that file. I tried both manually and using the search option, but it does not appear anywhere. I will try againt today.
Thanks for checking again, @markovsites. If TestCheckout.php doesn’t appear in your file system, then the next step is to confirm exactly which plugin or process is calling it.
Please do the following so we can narrow it down:
- Go to WooCommerce → Status → Logs.
Open the most recent fatal-error log and copy the full stack trace around the TestCheckout.php reference. Sometimes the file name appears inside a plugin namespace or a custom class, which helps identify the source even if the actual file isn’t present.
- Check for must-use plugins.
Go to Plugins → Must-Use. Sometimes hosts or custom integrations load files that won’t appear in the normal plugin list.
- If you use Elementor Pro, check if any custom checkout-related experiments, custom code snippets, or template overrides were added recently in Elementor → Custom Code or Elementor → Templates.
- If you have a mu-plugin folder or a code snippets plugin, please confirm whether any snippet mentions “TestCheckout” or modifies checkout validation.
Once you share the trace from the log (the lines before/after the TestCheckout reference), we can identify exactly which component is calling it and guide you from there.
It’s been a while since we heard back from you for this reason we are closing this thread.
If WooCommerce has been useful for your store and you appreciate the support you’ve received, we’d truly appreciate it if you could leave us a quick review here:
https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/#new-post
Feel free to open a new forum topic if you run into any other problem.