Fatal error: require_once(): Failed opening required …

  • Resolved nataliefaith02

    (@nataliefaith02)


    1 year, 9 months ago

    There’s an issue with the checkout page where a customer has to enter details on the address 2 line even though it’s not required. (Side note, is there a way to remove this field?)

    I assume this was due to a bug probabaly caused by not doing a few updates like PHP, plugin, theme and new wordpress updates.

    And while doing these updates a number of error messages came up:

    Fatal error: require_once(): Failed opening required ‘/home/redrooaustralia/public_html/wp-content/themes/Divi/includes/builder/api/DiviExtensions.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in /home/redrooaustralia/public_html/wp-content/themes/Divi/includes/builder/framework.php on line 163


    Fatal error: require_once(): Failed opening required ‘/home/redrooaustralia/public_html/wp-content/plugins/pixelyoursite/vendor/composer/autoload_static.php’ (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in /home/redrooaustralia/public_html/wp-content/plugins/pixelyoursite/vendor/composer/autoload_real.php on line 31

    Warning: include(): Failed opening ‘/home/redrooaustralia/public_html/wp-content/plugins/wordpress-seo/vendor/composer/../../src/integrations/admin/background-indexing-integration.php’ for inclusion (include_path=’.:/opt/cpanel/ea-php74/root/usr/share/pear’) in?/home/redrooaustralia/public_html/wp-content/plugins/download-monitor/vendor/composer/ClassLoader.php?on line?582

    ^ This last one happened after I tried to update the WooCommerce Database.

    I can see a few refer to php74 so could it be from when I updated the webiste PHP from 7.4 to 8.0?

    My team also had issues recieving emails after an order was made, and when going to Woocommerce > Settings > Emails and reviewing “New Order” I saw a numbe rof other fatel errors, which have now since disappeared since changed my downloadable products from Force Download to Redirect (that was suggested in another Q&A on this forum).

    Do you have any advice or guidance as to why I’m going these error messages? And how to fix some of them so the site is less buggy and more functional again?

    The page I need help with: [log in to see the link]

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

  • Hi @nataliefaith02

    Thanks for reaching out!

    There’s an issue with the checkout page where a customer has to enter details on the address 2 line even though it’s not required. (Side note, is there a way to remove this field?)

    To better picture what you are referring to here, can you please share with us a clear screenshot of what you see on your end so that we could address you more effectively?

    If you don’t already have a screenshot service installed, you can try https://snipboard.io. You can share the direct link to the image as a response to this topic.

    Meanwhile, can you please share what payment gateway was used that caused this error? Checking your site’s checkout page, I can see that you have Paypal and Stripe as the payment gateways.

    As for the error logs above, these are all pointing to third-party plugins on your site: Divi Theme, PixelYourSite, and Download Monitor respectively.

    Since these are third-party plugins that we don’t provide support for based on our Support Policy, I recommend that you reach out to the developers of the plugin for further assistance. They will be better equipped to help you resolve any issues you’re experiencing with the plugin.

    My team also had issues recieving emails after an order was made, and when going to Woocommerce > Settings > Emails and reviewing “New Order” I saw a numbe rof other fatel errors, which have now since disappeared since changed my downloadable products from Force Download to Redirect (that was suggested in another Q&A on this forum).

    Once again, a screenshot would be helpful as to what error message are you referring to here.

    For us to investigate your issue further, I’d like to understand your site properly. Please share your System Status Report that you can find via WooCommerce > Status. Select Get system report and then Copy for support. Once you’ve done that, you can paste it into your reply here.

    If you could also provide the fatal error logs (if any) under WooCommerce > Status > Logs.

    You could copy and paste your reply here or paste it via https://gist.github.com/ and send the link here.

    Thanks!

    Thread Starter nataliefaith02

    (@nataliefaith02)

    Thanks for your response. The checkout street address was fixed, but there are more/ new error messages:

    As for the error logs above, these are all pointing to third-party plugins on your site: Divi Theme,?PixelYourSite, and?Download Monitor?respectively.

    I know the error messages are pointing to plugins but there weren’t any error message prior to updates to Woocommerce.

    The new error message refers to:

    woocommerce-services.php & LiteSpeed Cache autoload.php causing trouble but these issues didn’t arise until PHP, WordPress & WooCommerce were updates to the newest versions recently. Screenshot attached.

    When reviewing the WooCommerce Status Report it all looks good apart from Cart & Checkout pages:

    When trying to edit the Cart or Checkout pages I’m met with this error message:

    Have you seen this error before? Surely it can’t be all the plugins. It has to be something more specific.

    I’ll send you a copy of the system report via email.

    Plugin Support John Coy a11n

    (@johndcoy)

    Automattic Happiness Engineer

    Hi @nataliefaith02

    I know the error messages are pointing to plugins but there weren’t any error message prior to updates to Woocommerce.

    Issues don’t typically arise until changes are made. If a plugin is not compatible with the most recent version of another plugin, then errors are expected.

    The new error message refers to:

    woocommerce-services.php & LiteSpeed Cache autoload.php causing trouble but these issues didn’t arise until PHP, WordPress & WooCommerce were updates to the newest versions recently. Screenshot attached.

    The same reasoning applies here. However, the errors from Litespeed and WooCommerce Services, are likely just a domino effect of code conflicts earlier in the scripts. WooCommerce Shipping & Tax ( WooCommerce Services ) works as expected with the most recent version so something unique about this install is causing the issue.

    Have you seen this error before? Surely it can’t be all the plugins. It has to be something more specific.

    Fatal errors can be common when updates are applied. When the code from plugins make up a significant amount of the codebase of the site, the potential of code errors should not be underestimated. Especially when the combination of plugins for each site makes each site unique.

    For this reason, we created a support page entirely for updating WooCommerce:

    https://woocommerce.com/document/how-to-update-woocommerce/

    To ensure the plugins from WooCommerce.com are working as expected, try switching back to a default theme like Twenty Twenty-Three and disabling all plugins except for WooCommerce to see if this resolves the problem.

    If this fixes the issue, re-enable each plugin one at a time, then the theme, until you find the one causing the conflict.

    Here is a link that better outlines that process:

    https://docs.woocommerce.com/document/woocommerce-self-service-guide/#section-4

    You can also work with your web host and the PHP errors they store, to pinpoint the specific cause.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal error: require_once(): Failed opening required …’ is closed to new replies.