Fatal Error
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
Quote from dan on September 9, 2026, 00:42Howdy!
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, FOX - Currency Switcher Professional for WooCommerce.
FOX 1.5.3
WooCommerce HPOS enabled
WooCommerce Payments Jetpack Sync running via WP-CronWoocsHpos->getOrderScreenId()callswc_get_page_screen_id()
PHP 8.5.4
WordPress 7.1
Howdy!
WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
In this case, WordPress caught an error with one of your plugins, FOX - Currency Switcher Professional for WooCommerce.
FOX 1.5.3
WooCommerce HPOS enabled
WooCommerce Payments Jetpack Sync running via WP-CronWoocsHpos->getOrderScreenId() calls wc_get_page_screen_id()
PHP 8.5.4
WordPress 7.1
Quote from Alex Dev on September 9, 2026, 20:04Hello
Thank you for the report.
Please send us the debug log. You can get it either with a plugin, for example WP Debugging together with Error Log Monitor from the WordPress repository, or manually by adding these lines to wp-config.php above the line "That's all, stop editing" and then reading wp-content/debug.log:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );We need to see the exact scenario in which the error occurs, with the file and the line number, because it does not reproduce on our side. We run HPOS on our development site and cannot trigger it there.
We do have a theory, and there is something you can try right away. Open the file classes/woocs_hpos.php in the plugin folder and replace the getOrderScreenId function with this version:
public function getOrderScreenId(): string { if (!function_exists('wc_get_container') || !class_exists('Automattic\WooCommerce\Utilities\OrderUtil') || !function_exists('wc_get_page_screen_id') || !class_exists('WC_Admin_Menus')) { return ''; } // @phpstan-ignore-next-line $screen = wc_get_container()->get(HposController::class)->custom_orders_table_usage_is_enabled() ? wc_get_page_screen_id('shop-order') : 'shop_order'; return $screen; }Please make a backup of the file first, and note that this is a manual edit, so it will be overwritten the next time you update the plugin. The change will be included in the next release.
After applying it, tell us whether anything changed on your side. Together with the log that will let us confirm the cause.
Best regards
Alex
Hello
Thank you for the report.
Please send us the debug log. You can get it either with a plugin, for example WP Debugging together with Error Log Monitor from the WordPress repository, or manually by adding these lines to wp-config.php above the line"That's all, stop editing" and then reading wp-content/debug.log:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
We need to see the exact scenario in which the error occurs, with the file and the line number, because it does not reproduce on our side. We run HPOS on our development site and cannot trigger it there.
We do have a theory, and there is something you can try right away. Open the file classes/woocs_hpos.php in the plugin folder and replace the getOrderScreenId function with this version:
public function getOrderScreenId(): string {
if (!function_exists('wc_get_container') || !class_exists('Automattic\WooCommerce\Utilities\OrderUtil') || !function_exists('wc_get_page_screen_id') || !class_exists('WC_Admin_Menus')) {
return '';
}
// @phpstan-ignore-next-line
$screen = wc_get_container()->get(HposController::class)->custom_orders_table_usage_is_enabled() ? wc_get_page_screen_id('shop-order') : 'shop_order';
return $screen;
}Please make a backup of the file first, and note that this is a manual edit, so it will be overwritten the next time you update the plugin. The change will be included in the next release.
After applying it, tell us whether anything changed on your side. Together with the log that will let us confirm the cause.
Best regards
Alex
Quote from Alex Dev on September 18, 2026, 17:18Hello
Update is just done (v.1.5.4), and fix is there
Hello
Update is just done (v.1.5.4), and fix is there