Backend “Home”

  • Resolved josssv

    (@josssv)


    3 months ago

    I have realized that when I go to the Woocommerce -> Home, the inbox often cannot load and the shop visibility shows different e.g. “live” when it should be “coming soon”.

    When I did a bit deeper into logs and https calls, I see a good number of 500 and 503 responses. With regards the logs I see what shows below:

    2024-08-20T15:13:15+00:00 CRITICAL require(): Failed opening required ‘[my-path]/wp-content/plugins/elementor/modules/nested-accordion/module.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) CONTEXT: {“error”:{“type”:64,”file”:”[my-path]/wp-content/plugins/elementor/includes/autoloader.php”,”line”:295},”backtrace”:[{“file”:”‘[my-path]/wp-content/plugins/woocommerce/includes/class-woocommerce.php”,”line”:359,”function”:”critical”,”class”:”WC_Logger”,”type”:”->”},{“function”:”log_errors”,”class”:”WooCommerce”,”type”:”->”}]}
    2024-08-20T15:13:18+00:00 CRITICAL require(): Failed opening required ”[my-path]/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version2/class-wc-rest-coupons-v2-controller.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) CONTEXT: {“error”:{“type”:64,”file”:”‘[my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php”,”line”:90},”backtrace”:[{“file”:”‘[my-path]/wp-content/plugins/woocommerce/includes/class-woocommerce.php”,”line”:359,”function”:”critical”,”class”:”WC_Logger”,”type”:”->”},{“function”:”log_errors”,”class”:”WooCommerce”,”type”:”->”}]}
    2024-08-20T15:13:18+00:00 CRITICAL require(): Failed opening required ”[my-path]/wp-content/plugins/elementor/core/common/app.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) CONTEXT: {“error”:{“type”:64,”file”:”‘[my-path]/wp-content/plugins/elementor/includes/autoloader.php”,”line”:295},”backtrace”:[{“file”:”‘[my-path]/wp-content/plugins/woocommerce/includes/class-woocommerce.php”,”line”:359,”function”:”critical”,”class”:”WC_Logger”,”type”:”->”},{“function”:”log_errors”,”class”:”WooCommerce”,”type”:”->”}]}

    Apparently, all works but, critical errors are never nice to have, are they? Astra recently released version 4.8. This has been happening with previous and current versions. To the question, “do files exist?” Yes, I have checked the files and they are there and have the same access rights as all other files, so it should not be a problem from that angle. I wonder if this is Astra or Woocommerce issue.

    Any guidance for how to solve these issues would be welcomed.

Viewing 9 replies - 1 through 9 (of 9 total)

  • Hey there, @josssv! Thanks for contacting us. I’m happy to help you.

    The errors you are seeing indicate that there’s an error with Elementor.

    Can you please run a conflict test to see if something external is interfering with this?

    To test, you’ll first want to change the theme on your site to Storefront, then check to see if the issue is still present. If that resolves the issue, you’ll want to get in touch with your theme’s developer and see if they have an update or fix for you.

    If changing the theme doesn’t help, you’ll want to deactivate all plugins except for WooCommerce and Elementor and take a look. If that fixes the problem, re-enable the other plugins one by one (gradually), checking after each, to see where the issue is coming from.

    If the issue persists, please also deactivate Elementor, leaving only Woo active to check.

    — Be sure you have a good backup in place of your full site and database. You can ask your host for backup functionality or you can consider using a service like Jetpack. If something goes wrong, you will be able to restore it.

    — It is important to consider as well a staging functionality in case you would not like to touch your production site (you can ask your host if they offer this service), or you can use WP Staging for quickly spinning up a new test site.

    You can find more about this in this guide.

    Please let us know about your findings.

    Have a wonderful day!

    Thread Starter josssv

    (@josssv)

    Thanks for your quick response. There might certainly be something between Elementor/Astra/Woocommerce. I first thought it could be related to Woocommerce because the error ONLY happens when entering the Woocommerce -> Home. It does not occur anywhere else. In the backend (Admin view), I typically read that there is a problem to open the “inbox” or with the stats. Jetpack errors are always there too (jetpack-autoloader/class-php-autoloader.php, the magic line 90)

    [19-Aug-2024 21:57:37 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/CheckoutOrderSummaryShippingBlock.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    [19-Aug-2024 21:58:00 UTC] PHP Notice: require(): read of 2921 bytes failed with errno=12 Cannot allocate memory in [my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    [19-Aug-2024 21:58:00 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]/wp-content/plugins/woocommerce/src/Admin/DeprecatedClassFacade.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    [19-Aug-2024 21:58:03 UTC] PHP Notice: require(): read of 9217 bytes failed with errno=12 Cannot allocate memory in [my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    [19-Aug-2024 21:58:03 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/OrderConfirmation/Totals.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    Even I see some “allocate memory” errors, I can speculate that the source problem is elsewhere as there are 3GB of memory and it is just some few bytes… so there may be something else interfering. I will do some checks as suggested, nonetheless.

    Thread Starter josssv

    (@josssv)

    And just attempting few minutes ago – I see some elementor issues, but woocommerce and jetpack-autoloader are really coping with all. And “/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90” is often a common denominator every time there are faults.

    [20-Aug-2024 17:52:12 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/PageContentWrapper.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:52:12 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Blocks/BlockTypes/CheckoutOrderSummaryCouponFormBlock.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:52:12 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/elementor/app/modules/import-export/utils.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/elementor/includes/autoloader.php on line 295
    [20-Aug-2024 17:52:12 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/elementor/core/admin/menu/admin-menu-manager.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/elementor/includes/autoloader.php on line 295
    [20-Aug-2024 17:52:39 UTC] PHP Fatal error: require_once(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/elementor/includes/base/element-base.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/elementor/includes/managers/elements.php on line 359
    [20-Aug-2024 17:52:44 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/includes/rest-api/Controllers/Version1/class-wc-rest-webhooks-v1-controller.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:57:20 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Admin/API/ProductReviews.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:57:20 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Admin/API/Reports/PerformanceIndicators/Controller.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:57:20 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Admin/API/Reports/Coupons/Controller.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90
    [20-Aug-2024 17:57:52 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/elementor//includes/settings/settings.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/elementor/includes/autoloader.php on line 295
    [20-Aug-2024 17:57:52 UTC] PHP Fatal error: require(): Failed opening required ‘[my-path]shop-stagged/wp-content/plugins/woocommerce/src/Admin/Features/PaymentGatewaySuggestions/PaymentGatewaysController.php’ (include_path=’.:/opt/alt/php74/usr/share/pear’) in [my-path]shop-stagged/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 90

    Plugin Support omarfpg a11n

    (@omarfpg)

    Hi @josssv,

    Thank you for the additional details. This typically means a third-party plugin is interfering; we say this from previous instances we’ve seen of this error and because using WooCommerce on its own (or even with Jetpack) doesn’t cause these errors, especially because you’ve already confirmed the files are there, and the file permissions are ok!

    Have you had a chance to run a full conflict test as suggested by my colleague here? You can also learn more here.

    Cheers!
    -OP

    Thread Starter josssv

    (@josssv)

    Thanks OP! Yeah, I have tried to deactivate some of the plugins and activate them. Changing the template did not fix it; however, it seems there is something with Elementor. Apparently, deactivating it seemed to fix it.

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @josssv

    From the information you’ve shared, it looks like the Elementor plugin may be causing the issues you’ve been experiencing. Since you’ve mentioned that deactivating Elementor seemed to resolve the problem, it suggests that there might be a conflict between Elementor and other components of your website.

    To isolate the issue further, I recommend contacting Elementor’s support team and sharing the error logs with them. They might be able to provide more insights into what could be causing these critical errors.

    In the meantime, you might consider using an alternative page builder or, if possible, a previous version of Elementor that didn’t cause these issues while you wait for a resolution.

    I hope this provides some clarity. Please let us know if you have any other questions!

    Thread Starter josssv

    (@josssv)

    Hi! I just saw that Woocommerce released a new update to revert some changes in previous updates. One of them related to the “Rest-api”. “REST-API” was one of the things that was returning fatal errors. Do you know if other users had similar problems as mine? After the update, I lightly performed a couple of tests and, surprisingly, no errors. But I keep you posted if I get them back and if so, what was causing them.

    Thread Starter josssv

    (@josssv)

    I shall correct the above. The issue appeared again after a while. I am still checking with Elementor team.

    Plugin Support Rajesh K. (woo-hc)

    (@rajeshml)

    Hello @josssv,

    Thank you for keeping us updated on the status.

    Please let us know how it goes with the Elementor team. Feel free to reach out if you have additional questions.

    Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.