Hi there @meroving ,
Thank you for bringing this into our attention and sorry to hear about it random occurrence; that’s actually the first time seeing anything similar.
Could you please share a bit more information so we can investigate further?
- The WooCommerce version you’re using.
- The WordPress and PHP versions of your site.
- The full error stack trace, since the one shown in the post looks truncated.
- A short list of the plugins active when the issue occurs – for example, if you’ve managed to isolate it to WP Activity Log, WooCommerce, and a few others, please let us know which ones.
- If possible, the exact steps to reproduce the error? This will surely be important just to have some idea how and when this occurred.
- Last but not least, can you describe how this affects the site? Was it only a one-timer, or did it caused a plugin or site crash of any sort?
This information will help us reproduce the issue and pinpoint what’s causing it much faster, so the more details provided, the better.
Thanks in advance for your help in narrowing this down.
Hello Lucian,
thanks for the fast response!
Woo: 10.3.3
PHP: 8.3.26
Full error – unfortunately this was the full we received in email. On Godaddy (managed WP hosting plan) we have not got the right to check the WP debug log, so I cannot tell.
Plugins (all is up to date):
- Check & Log Email – Easy Email Testing & Mail logging
- CoBlocks
- Code Snippets
- Contact Form 7
- Contact Form 7 Connector
- Contact Form CFDB7
- Extra Fees for WooCommerce
- Google for WooCommerce
- Pinterest for WooCommerce
- Rank Math SEO
- Rank Math SEO PRO
- User Role Editor
- USPS Checkout Fields (project custom plugin)
- WooCommerce
- WooCommerce Address Validation
- WooCommerce Bulk Stock Management
- WooCommerce Checkout Field Editor
- WooCommerce PayPal Payments
- WooCommerce.com Update Manager
- Wordfence Security
- WP Activity Log
- WP Rocket
- WPCode Lite
- XPS Ship Integration
Steps to reproduce: I could not. We just got these emails daily 1-2. Unfortunately, there is no way to one by one disable the plugins to figure out the issue because the site is live. This issue started with the previous version and then continued with the 5.3.3
However, I understand that fixing something without the proper error message it is almost impossible. In the next 2 days I will try to retrieve the error message from the hosting company.
Regards, M
Hello @lucianwpwhite ,
I have contacted with GoDaddy and there is no option for us to see the error log… that is just nonsense.
Is there any way from my previous post to figure out what can be the issue here?
Regards, M
Hello again @meroving !
Thank you for the update!
Unfortunately, without the full error log and detailed steps to reproduce the issue, it’s quite difficult for us to pinpoint what might be happening.
If possible, please try to reproduce this on a staging site instead of your live environment – that will make troubleshooting safer and easier. Once you’ve isolated it there, kindly share the following details with us:
- The exact error message or PHP log output
- The steps that consistently trigger the error.
- The plugins involved into this error (it would be useful if you could narrow this down by disabling some other plugins as well and only keep the ones involved)
With that information, we’ll be able to investigate further and advise on the best next steps.
Many thanks for your cooperation!
Hello @lucianwpwhite !
Unfortunately on Godaddy on this tier this is not possible. I will try to solve this to migrate the site elsewhere for the test but it will not be fast. I guess I’ll be back with a report a few weeks later.
Regards, M
Thank you for the follow up @meroving !
Feel free to also reach out directly via email at [email protected] once the new details arrive (especially if they contain sensitive site info etc). This way we can exchange information easily and investigate this further 1 to 1.
Looking forward on your updates!
Hi there,
My client’s website, also hosted on GoDaddy, encountered the same error. (@meroving Enabling debugging on GoDaddy’s Managed WordPress is a little confusing due to custom settings, but it’s possible. You have to define the WP_DEBUG constant above the line require_once __DIR__ . '/../configs/wp-config-hosting.php'; in your site’s wp-config.php.)
@lucianwpwhite Here’s the full stack trace:
[26-Jan-2026 14:56:11 UTC] PHP Fatal error: Uncaught TypeError: strpos(): Argument #2 ($needle) must be of type string, false given in /dom680732/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php:290
Stack trace:
#0 /dom680732/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php(290): strpos('https://cortile...', false)
#1 /dom680732/wp-includes/class-wp-hook.php(341): WSAL\WP_Sensors_Helpers\WooCommerce_Sensor_Helper_Second::editing_product(Object(WP_Post))
#2 /dom680732/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(Object(WP_Post), Array)
#3 /dom680732/wp-includes/plugin.php(522): WP_Hook->do_action(Array)
#4 /dom680732/wp-admin/edit-form-advanced.php(482): do_action('post_edit_form_...', Object(WP_Post))
#5 /dom680732/wp-admin/post.php(206): require('/dom680732/wp-a...')
#6 {main}
thrown in /dom680732/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php on line 290
I fixed the error by changing line 290 from this:
$current_path = isset( $server_array['SCRIPT_NAME'] ) ? \sanitize_text_field( \wp_unslash( $server_array['SCRIPT_NAME'] ) ) . '?post=' . $product->ID : false;
to this:
$current_path = isset( $server_array['SCRIPT_NAME'] ) ? \sanitize_text_field( \wp_unslash( $server_array['SCRIPT_NAME'] ) ) . '?post=' . $product->ID : '';
Saul
Hey Saul!
Thank you, I’ll try this!!
Regards, M
-
This reply was modified 4 months ago by
meroving.
Hello guys @meroving @saulbaizman
We have just released version 5.6.0 on which our dev team has applied some tweaks which should be covering this error. Can you give it a try and let me know how it goes for you?
If there’s anything that you would like to share, or if there are any other issues, please open a new thread with the new error/details, instead of sharing them here, so we can keep things organized, and for a better communication.
I do appreciate all your ongoing cooperation and help on this one and looking forward on your update!
Hello @lucianwpwhite !
Thanks, already updated! I’ll let you know whether we have any issue or not.
Regards, M
-
This reply was modified 4 months ago by
meroving.