500 internal after new update
-
Hi, we just faced a 500 internal server error after the 2.1.8 update so We downgraded.
Here is the call stack:[17-Oct-2018 07:44:46 UTC] PHP Fatal error: Uncaught TypeError: Argument 1 passed to WPDesk\Mutex\WordpressPostMutex::fromOrder() must be an instance of WPDesk\Mutex\WC_Order, instance of WC_Order given, called in /home/sayman/public_html/wp-content/plugins/flexible-shipping/classes/flexible-shipping-plugin.php on line 187 and defined in /home/sayman/public_html/wp-content/plugins/flexible-shipping/vendor/wpdesk/wp-mutex/src/WPDesk/Mutex/WordpressPostMutex.php:53
Stack trace:
#0 /home/sayman/public_html/wp-content/plugins/flexible-shipping/classes/flexible-shipping-plugin.php(187): WPDesk\Mutex\WordpressPostMutex::fromOrder(Object(WC_Order))
#1 /home/sayman/public_html/wp-includes/class-wp-hook.php(288): WPDesk_Flexible_Shipping_Plugin->add_flexible_shipping_order_meta_on_checkout(Object(WC_Order))
#2 /home/sayman/public_html/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(”, Array)
#3 /home/sayman/public_html/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#4 /home/sayman/public_html/wp-content/plugins/woocommerce/includes/class-wc- in /home/sayman/public_html/wp-content/plugins/flexible-shipping/vendor/wpdesk/wp-mutex/src/WPDesk/Mutex/WordpressPostMutex.php on line 53
-
If you are not the original topic poster and if you need support then per the forum guidelines please start your own topic.
https://www.ads-software.com/support/guidelines/#post-in-the-best-place
You can do so here.
https://www.ads-software.com/support/plugin/flexible-shipping/#new-post
That’s how these forums work, do not pile onto someone else’s topic.
- The topic ‘500 internal after new update’ is closed to new replies.
