Conversation
supportThe website is not fully updated, so that could very well be the issue, but I wanted to post the error either way. WordPress version 5.8 Current theme: XXXXXXXXXXXXX (version 1.0.2) Current plugin: Order Status History for WooCommerce (version 1.7.2) PHP version 7.4.24 Error Details ============= An error of type E_ERROR was caused in line 115 of the file /nas/content/live/XXXXXXXXXXXXX/wp-content/plugins/order-status-history-for-woocommerce/includes/class_osh.php. Error message: Uncaught Error: Class 'Automattic\Jetpack\Constants' not found in /nas/content/live/XXXXXXXXXXXXX/wp-content/plugins/order-status-history-for-woocommerce/includes/class_osh.php:115 Stack trace: #0 /nas/content/live/XXXXXXXXXXXXX/wp-includes/class-wp-hook.php(303): oshwoo\osh->enqueue_user_agent_scripts('plugins.php') #1 /nas/content/live/XXXXXXXXXXXXX/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #2 /nas/content/live/XXXXXXXXXXXXX/wp-includes/plugin.php(470): WP_Hook->do_action(Array) #3 /nas/content/live/XXXXXXXXXXXXX/wp-admin/admin-header.php(102): do_action('admin_enqueue_s...', 'plugins.php') #4 /nas/content/live/XXXXXXXXXXXXX/wp-admin/plugins.php(603): require_once('/nas/content/li...') #5 {main} thrown
Thanks for your report. What WooCommerce (WC) version are you using? Class 'Automattic\Jetpack\Constants' not found implies something isn’t right with the WC installation, as this is a call we make to functionality available into their code. Upon activation, our plugin checks for WC being installed, but if the WC installation is buggy/incompatible/unavailable for some reason, unusual errors like this might occur because of said dependencies inside our code. So please make sure WC is properly working before activating our plugin.
I’m sure it’s just an issue of my website being outdated, it hasn’t been updated in a long time, but WC is working just fine. It’s running WC Version 3.5.9
This should be it. WC is currently at 5.7.1 . WC 3.5.9 is indeed ancient, and probably has a completely different code organization, hence the namespace Automattic\Jetpack\Constants reference fail. My end I should at least update the minimum WC version now, but that won’t help making my plugin work any better for you, I’m afraid.
I’ve looked a bit more into this, and it seems I’m not using much direct references to WC code. For the next update I’ve tweaked the code that gave you an issue to bypass such WC references. If you’re willing to test further, I can prepare a dev version of the plugin for you, so you can see now how well it would work with your version of WC. If you may encounter any further issues, you can report them back here so I can attempt to fix them.
Thanks for your report. What WooCommerce (WC) version are you using? Class 'Automattic\Jetpack\Constants' not found implies something isn’t right with the WC installation, as this is a call we make to functionality available into their code. Upon activation, our plugin checks for WC being installed, but if the WC installation is buggy/incompatible/unavailable for some reason, unusual errors like this might occur because of said dependencies inside our code. So please make sure WC is properly working before activating our plugin.
I’m sure it’s just an issue of my website being outdated, it hasn’t been updated in a long time, but WC is working just fine. It’s running WC Version 3.5.9
This should be it. WC is currently at 5.7.1 . WC 3.5.9 is indeed ancient, and probably has a completely different code organization, hence the namespace Automattic\Jetpack\Constants reference fail. My end I should at least update the minimum WC version now, but that won’t help making my plugin work any better for you, I’m afraid.
I’ve looked a bit more into this, and it seems I’m not using much direct references to WC code. For the next update I’ve tweaked the code that gave you an issue to bypass such WC references. If you’re willing to test further, I can prepare a dev version of the plugin for you, so you can see now how well it would work with your version of WC. If you may encounter any further issues, you can report them back here so I can attempt to fix them.