• Resolved dimitrisv

    (@dimitrisv)


    We are getting errors like this on the checkout. We had to de-activate it after the fourth (in an hour) crash.

    An error of type E_ERROR was caused in line 354 of the file /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/log-handlers/class-wc-log-handler-file.php. Error message: Uncaught Error: Call to undefined method Automattic\WooCommerce\Utilities\LoggingUtil::get_log_directory() in /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/log-handlers/class-wc-log-handler-file.php:354
    Stack trace: 0 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/gateways/paypal/includes/settings-paypal.php(58): WC_Log_Handler_File::get_log_file_path(‘paypal’) 1 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/gateways/paypal/class-wc-gateway-paypal.php(335): include(‘/www/ffdemo_565…’) 2 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/gateways/paypal/class-wc-gateway-paypal.php(90): WC_Gateway_Paypal->init_form_fields() 3 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-wc-payment-gateways.php(403): WC_Gateway_Paypal->__construct() 4 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-wc-payment-gateways.php(89): WC_Payment_Gateways->should_load_paypal_standard() 5 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-wc-payment-gateways.php(76): WC_Payment_Gateways->init() 6 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-wc-payment-gateways.php(49): WC_Payment_Gateways->__construct() 7 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-woocommerce.php(1022): WC_Payment_Gateways::instance() 8 /www/ffdemo_565/public/wp-content/plugins/woocommerce/includes/class-woocommerce.php(179): WooCommerce->payment_gateways() 9 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/Schemas/V1/CheckoutSchema.php(141): WooCommerce->__get(‘payment_gateway…’) 10 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/Schemas/V1/AbstractSchema.php(64): Automattic\WooCommerce\StoreApi\Schemas\V1\CheckoutSchema->get_properties() 11 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/AbstractRoute.php(87): Automattic\WooCommerce\StoreApi\Schemas\V1\AbstractSchema->get_item_schema() 12 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/AbstractRoute.php(271): Automattic\WooCommerce\StoreApi\Routes\V1\AbstractRoute->get_item_schema() 13 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/Routes/V1/Checkout.php(72): Automattic\WooCommerce\StoreApi\Routes\V1\AbstractRoute->get_context_param(Array) 14 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/RoutesController.php(125): Automattic\WooCommerce\StoreApi\Routes\V1\Checkout->get_args() 15 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/RoutesController.php(79): Automattic\WooCommerce\StoreApi\RoutesController->register_routes(‘v1’, ‘wc/store’) 16 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/StoreApi/StoreApi.php(27): Automattic\WooCommerce\StoreApi\RoutesController->register_all_routes() 17 /www/ffdemo_565/public/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\StoreApi\StoreApi->Automattic\WooCommerce\StoreApi{closure}(Object(WP_REST_Server)) 18 /www/ffdemo_565/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) 19 /www/ffdemo_565/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 20 /www/ffdemo_565/public/wp-includes/rest-api.php(597): do_action(‘rest_api_init’, Object(WP_REST_Server)) 21 /www/ffdemo_565/public/wp-includes/rest-api.php(555): rest_get_server() 22 /www/ffdemo_565/public/wp-includes/rest-api.php(2922): rest_do_request(Object(WP_REST_Request)) 23 [internal function]: rest_preload_api_request(Array, ‘/wc-analytics/r…’) 24 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(145): array_reduce(Array, ‘rest_preload_ap…’) 25 /www/ffdemo_565/public/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings(Array) 26 /www/ffdemo_565/public/wp-includes/plugin.php(205): WP_Hook->apply_filters(Array, Array) 27 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(61): apply_filters(‘woocommerce_adm…’, Array) 28 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(268): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin{closure}() 29 /www/ffdemo_565/public/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(393): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data() 30 /www/ffdemo_565/public/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data(”) 31 /www/ffdemo_565/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) 32 /www/ffdemo_565/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 33 /www/ffdemo_565/public/wp-admin/includes/template.php(2228): do_action(‘admin_print_foo…’) 34 /www/ffdemo_565/public/wp-admin/update.php(53): iframe_footer() 35 {main}

      thrown



Viewing 11 replies - 16 through 26 (of 26 total)
  • Thread Starter dimitrisv

    (@dimitrisv)

    I have never received a response from you! This is why I am complaining in here.

    Please resend it to me your response. Or tell me who is suppossed to be the sender to check the junk folder.

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello?@dimitrisv

    You reached out to us through the support board on Thursday at 9:59 AM, and I replied on the same day at 11:27 AM. If you can’t find any information related to the PPC-1243 case in your email, I will recreate it and invite you to our Jira Support Management.

    Best regards,
    Krystian

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @dimitrisv

    I have created ticket PPC-1246 and sent an invitation to the same email address you used initially. Please check your email.

    Thank you in advance.

    Best regards,
    Krystian

    Thread Starter dimitrisv

    (@dimitrisv)

    First of all HUGE and HUBLING apologies!

    Indeed the message had gone to the spam folder of my email (outlook btw) – its originating domain did not help either.

    Yes I will provide you with full access (and sftp access) to our beta sites/server for you to have a look and hopefully sort out the issues.

    I have had a similar problem since patch. If PayPal is enabled, the product pages just crash out with a boat load of errors pointing at WooCommerce’s PayPal ‘plugin?’

    wordpress\/wp-content\/plugins\/woocommerce-paypal-payments\/modules\/ppcp-button\/src\/Assets\/SmartButton”]}

    etc etc..

    I was hoping someone at Woo would have fixed this borkage by now. But I suppose it’s my fault for using automatic updates switched on.

    Anywho, fingers crossed someone is working on this.. Coz I’ve only just migrated to Woo.. And I’m starting to think it wasn’t a great idea.

    Thread Starter dimitrisv

    (@dimitrisv)

    Yes they are working on it as we speak. I gave to the guys access in a problematic (for their plugin) installation and are looking into it.

    Fingers crossed they will sort it out soon.

    Good stuff. And thanks for starting this thread!!

    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello @rodhull

    Firstly, we recommend starting your own thread for assistance, as it’s our policy not to intervene in discussions about issues reported on behalf of other users. This is because the problem might stem from a different source. In your case, this is exactly what has happened—the issue you’re experiencing is unrelated to the one initially discussed in this thread.

    In conclusion, since your issue is different, we will not address it in this thread. Please create your new thread, and we’ll try to address this as soon as possible.

    Thank you for your understanding.

    Kind regards,
    Krystian

    Thread Starter dimitrisv

    (@dimitrisv)

    Just to convey here that in our case the resolution was as follows:

    1. Downgrade to Woocommerce 8.7. As you downgrade in our case you will get errors like this:


    WordPress ?κδοση 6.5.2
    Ενεργ? θ?μα: Presidential Noble (?κδοση 1.0.0)
    Τρ?χων πρ?σθετο: WooCommerce (?κδοση 8.7.0)
    ?κδοση PHP 8.2.18
    
    
    
    Λεπτομ?ρειε? σφ?λματο?
    ===========================================
    ?να σφ?λμα τ?που E_ERROR εντοπ?στηκε στη γραμμ? 226 του αρχε?ου public_html/wp-content/plugins/woocommerce/includes/wccom-site/class-wc-wccom-site.php. Κωδικ?? σφ?λματο?: Uncaught Error: Failed opening required 'public_html/wp-content/plugins/woocommerce/includes/wccom-site/rest-api/endpoints/class-wc-rest-wccom-site-status-controller.php' (include_path='.:/usr/share/php') in public_html/wp-content/plugins/woocommerce/includes/wccom-site/class-wc-wccom-site.php:226
    Stack trace:
    #0 public_html/wp-includes/class-wp-hook.php(324): WC_WCCOM_Site::register_rest_namespace()
    #1 public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #2 public_html/wp-content/plugins/woocommerce/includes/rest-api/Server.php(60): apply_filters()
    #3 public_html/wp-content/plugins/woocommerce/includes/rest-api/Server.php(43): Automattic\WooCommerce\RestApi\Server->get_rest_namespaces()
    #4 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\RestApi\Server->register_rest_routes()
    #5 public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #6 public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
    #7 public_html/wp-includes/rest-api.php(597): do_action()
    #8 public_html/wp-includes/rest-api.php(555): rest_get_server()
    #9 public_html/wp-includes/rest-api.php(2922): rest_do_request()
    #10 [internal function]: rest_preload_api_request()
    #11 public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Settings.php(143): array_reduce()
    #12 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Internal\Admin\Settings->add_component_settings()
    #13 public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #14 public_html/wp-content/plugins/woocommerce/src/Internal/Admin/WCAdminSharedSettings.php(61): apply_filters()
    #15 public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(268): Automattic\WooCommerce\Internal\Admin\WCAdminSharedSettings->Automattic\WooCommerce\Internal\Admin\{closure}()
    #16 public_html/wp-content/plugins/woocommerce/src/Blocks/Assets/AssetDataRegistry.php(384): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->execute_lazy_data()
    #17 public_html/wp-includes/class-wp-hook.php(324): Automattic\WooCommerce\Blocks\Assets\AssetDataRegistry->enqueue_asset_data()
    #18 public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
    #19 public_html/wp-includes/plugin.php(517): WP_Hook->do_action()
    #20 public_html/wp-admin/admin-footer.php(95): do_action()
    #21 public_html/wp-admin/update.php(186): require_once('...')
    #22 {main}
      thrown

    2. Re upgrade to 8.8.2

    No issue will be present.

    Me thinks that the issue was indeed due to various code merging issues in Woocommerce 8.8.1 and 8.8.2 in conjunction with 8.7 – So the paypal payments plugin was not at fault.

    I guess this has to do with the major refactoring/re-engineering of the whole Rest-api infrastructure to be released next month.

    The funny thing is that @inpsydekrystian had suggested to go to 8.8.1 and retry, which I did but to no avail. In other cases I either went back to 8.7 (and had the paypal payments plugin activated) or remained in 8.8.2 (without the paypal plugin).

    • This reply was modified 7 months ago by dimitrisv. Reason: spelling
    Plugin Support Krystian from Syde

    (@inpsydekrystian)

    Hello?@dimitrisv

    In my initial Jira response, I mentioned checking the latest WooCommerce development blog, where I found discussions about potential conflicts with version 8.8.1. These issues, mainly related to the Action Scheduler, are expected to be resolved in version 8.8.2. This problem in theory shouldn’t affect PayPal Payments, but it seems version 8.8.1 was at the core of the issue.

    I had indeed recommended version 8.8.1 based on updates seen on GitHub, not realizing this version had been deprecated. It turns out this was an unfortunate edge case, but luckily, WooCommerce has already removed the problematic version.

    If any further issues arise, please let us know. I’m glad to hear this situation has been resolved.

    Kind regards,
    Krystian

    Thread Starter dimitrisv

    (@dimitrisv)

    The peculiar thing is that – as most – I had never installed 8.8.1 in the first place.

    We only got notified for a new version with the 8.8.2 release!

    Anyway, the suggested, radical changes promise to make our sites much much more faster. Lets see – less than a month to go.

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘Crashes after update to 8.8.2’ is closed to new replies.