PHP Fatal error: Uncaught Error: Failed opening required

Hi, GiftUp!

I’m getting the same on my website @mtg169 and had to deactivate otherwise you can’t log in or access the admin area (the frontend seems to be fine).

I’ve included the warning with the website name redacted:

Warning: require_once(/www/example.com_424/public/wp-content/plugins/gift-up/blocks/src/apply-block/giftup-apply-block-integration.php): Failed to open stream: No such file or directory in /www/example.com_424/public/wp-content/plugins/gift-up/includes/class-giftup-woocommerce.php on line 72

The error too and the website name redacted:

Fatal error: Uncaught Error: Failed opening required '/www/example.com_424/public/wp-content/plugins/gift-up/blocks/src/apply-block/giftup-apply-block-integration.php' (include_path='/www/example.com_424/public/wp-content/plugins/post-smtp/includes/libs/HTMLPurifier:.:/usr/share/php:/www/example.com_424/public/wp-content/plugins/myworks-woo-sync-for-quickbooks-online/includes/lib/quickbooks-lib') in /www/example.com_424/public/wp-content/plugins/gift-up/includes/class-giftup-woocommerce.php:72 Stack trace: #0 /www/example.com_424/public/wp-includes/class-wp-hook.php(324): GiftUp_WooCommerce::woocommerce_register_cart_block('') #1 /www/example.com_424/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #2 /www/example.com_424/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #3 /www/example.com_424/public/wp-settings.php(727): do_action('init') #4 /www/example.com_424/public/wp-config.php(58): require_once('/www/example.co...') #5 /www/example.com_424/public/wp-load.php(50): require_once('/www/example.co...') #6 /www/example.com_424/public/wp-blog-header.php(13): require_once('/www/example.co...') #7 /www/example.com_424/public/index.php(17): require('/www/example.co...') #8 {main} thrown in /www/example.com_424/public/wp-content/plugins/gift-up/includes/class-giftup-woocommerce.php on line 72

Deactivating Gift Up solves the issue and site admin/login functionality is restored.

Thanks in advance,

Simon

@koanleeroy No worries, it happens and thanks for such a quick fix@mtg169

Both of the websites impacted now work with 3.0.1

Thank you again,

Simon