v 6.6.1

  • John Smith

    (@zeevousite)


    3 years, 11 months ago

    this version has issue and will break the site.
    I deactivated All plugins on one of my websites except the woocommerce version 6.6.1 and the pages took much time to load and they even did not loaded and faced to 500 server error timeout error. any help if possible. do not update instantly and make a back up first then you can revert back to old version.

    • This topic was modified 3 years, 11 months ago by John Smith.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Juan G. (woo-hc)

    (@judagutor)

    3 years, 11 months ago

    Hi @zeevousite!

    Thank you for your feedback.

    We test all the WooCommerce versions to work with your WordPress site, although there could be issues due to outdated software or setup.

    Kindly share the issue you have with us so we can take a further look, and we will be glad to help you find a solution.

    Cheers!

    Thread Starter John Smith

    (@zeevousite)

    3 years, 11 months ago

    sure thanks what should I share ?
    the result is that any page does not load at all and returns server error 500. the page has this paragraph:
    “Request Timeout
    This request takes too long to process, it is timed out by the server. If it should not be timed out, please contact administrator of this web site to increase ‘Connection Timeout’.”
    I checked log file it has no error log related to woocommerce. but I am sure that the problem is with woocommerce because I deactivated all and just woocommerce was active (v 6.6.1) and there was this issue.
    at the moment there is timeout limit 300 in wp-config.php. should I increase that?
    currently I use version 6.4.1 . what else should I share?

    • This reply was modified 3 years, 11 months ago by John Smith.
    Igor H

    (@ihereira)

    3 years, 11 months ago

    Hello,

    I’m sorry to hear that.

    do not update instantly and make a back up first then you can revert back to old version.

    You can use this plugin to rollback to previous version (if needed): https://wordpress.org/plugins/wp-rollback/

    the result is that any page does not load at all and returns server error 500

    To check better, can you please share a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Copy for support”. 

    We’ll look forward to hearing from you.

    Thread Starter John Smith

    (@zeevousite)

    3 years, 11 months ago

    I increased time out limit from 300 to 1000 but no success.

    [03-Jul-2022 16:02:43 UTC] PHP Fatal error:  require(): Failed opening required '/public_html/wp-content/plugins/woocommerce/src/Admin/Features/OnboardingTasks/TaskList.php' (include_path='.:/opt/cpanel/ea-php74/root/usr/share/pear') in /public_html/wp-content/plugins/woocommerce/vendor/jetpack-autoloader/class-php-autoloader.php on line 87

    this is the recent error that I get.
    I can not go to status page as far as it is not loading at all.
    but I can mention that I use some other plugins related to WooCommrce
    YITH WooCommerce Quick View

    BEAR – Bulk Editor and Products Manager Professional for WooCommerce
    weLaunch Framework
    WooCommerce Group Attributes
    WooCommerce PDF Invoices & Packing Slips
    WooCommerce PDF Invoices & Packing Slips Professional

    and a few others

    • This reply was modified 3 years, 11 months ago by John Smith.
    • This reply was modified 3 years, 11 months ago by John Smith.
    • This reply was modified 3 years, 11 months ago by John Smith.
    • This reply was modified 3 years, 11 months ago by John Smith.
    aetta

    (@chiape)

    3 years, 11 months ago

    Hi @zeevousite! Thanks for writing back!

    Have you uploaded your site content from a local installation?

    I am asking this because it sounds like an issue with your PHP autoloader file in your cPanel. Can you try to regenerate it?

    You may need to ask your hosting company to do it using Terminal or SSH.

    On the root of your site, you can try a cmd like this:

    composer update --no-scripts

    If you’re still having issues with that, I’d recommend checking your WordPress installation, and double-check all the file_dir paths that you’re using.

    I hope this helps!

    My very best,

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

The topic ‘v 6.6.1’ is closed to new replies.