WPIntell

Source evidence

Fatal error during update

Ship Estimate for WooCommerce · support · 2024-01-24T14:28:00+00:00

mixedsentiment
highseverity
0.88relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 25 rows with source links

16.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

21 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
titsmaker resolved
Hi, during updating to latest version (1.6.0) a fatal error has happened (I am using PHP 8.0 if it matters). Here’s a record from my log Fatal error: Uncaught Error: Call to a member function get_shipping_methods() on bool in /wp-content/plugins/wc-ship-est/wse_functions.php:829 Stack Trace 1. wse_ship_est() /wp-content/plugins/wc-ship-est/wse_functions.php:1068 2. wse_delivery_est() /wp-includes/class-wp-hook.php:324 3. WP_Hook->apply_filters() /wp-includes/class-wp-hook.php:348 4. WP_Hook->do_action() /wp-includes/plugin.php:517 5. do_action() /wp-admin/includes/template.php:2222 6. iframe_footer() /wp-admin/update.php:103 7. {main} thrown in /wp-content/plugins/wc-ship-est/wse_functions.php on line 829 Hi there, I will release a fix today. You may prepend line 829 with if(function_exists('get_shipping_methods'))... Does the error continue, or just during the update? Thank you for quick reaction. To date the error was thrown only during update but the site has low traffic, so no sound judgement can be made. Thank you for confirming. This should now be resolved in v 1.6.1 available now.

Comments

3 shown
RLDD 2024-01-24T16:24:00+00:00

Hi there, I will release a fix today. You may prepend line 829 with if(function_exists('get_shipping_methods'))... Does the error continue, or just during the update?

titsmaker 2024-01-24T17:42:00+00:00

Thank you for quick reaction. To date the error was thrown only during update but the site has low traffic, so no sound judgement can be made.

RLDD 2024-01-24T19:53:00+00:00

Thank you for confirming. This should now be resolved in v 1.6.1 available now.