• Resolved bluesapphiremedia

    (@bluesapphiremedia)


    Updated this plugin, which caused site to crash. Deactivated and reactivated, rolled back, and limiting access to other plugins on the Dashboard such as Wordfence settings. Deactivated until the error was fixed but nothing in the changeling for 2 weeks.

    If I now try to update I received “Update failed: There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.Learn more about troubleshooting WordPress.”

    Have rolled back WordPress and PHP to try and resolve and still nothing has worked.

    WordPress version 7.0
    Active theme: OceanWP (version 4.1.6)
    Current plugin: PPOM for WooCommerce (version 34.0.1)
    PHP version 8.5.6

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support rodicaelena

    (@rodicaelena)

    Hi,

    Thank you for writing! I am so sorry for the stress and frustration this crash has caused.

    When WordPress throws that “critical error” screen, it automatically sends an automated email to your site’s admin email address containing the technical details.

    Could you please check your inbox (and spam folder) for that email and reply to us with the exact error details listed there?

    We are looking for the lines that mention a “Fatal Error”—it usually points to a specific file path and line number (e.g., Fatal error: Uncaught Error... in /wp-content/plugins/... on line X).

    If you didn’t receive the email, here is how to find the error:

    1. Check your server logs: Log into your hosting account or access your site via FTP, and look for a file named error_log or debug.log inside your root directory or /wp-content/ folder. Paste the most recent lines here.
    2. Enable WP Debug: If no logs exist, open your wp-config.php file, change define('WP_DEBUG', false); to true, and add define('WP_DEBUG_LOG', true); right below it. Trigger the error once more, and it will write the exact conflict to a debug.log file in your /wp-content/ folder.

    Once we have that exact fatal error text, we can trace exactly why PPOM is conflicting with your environment and get this resolved for you.

    Kind regards!

    Thread Starter bluesapphiremedia

    (@bluesapphiremedia)

    Error Details

    =============

    An error of type E_ERROR was caused in line 1400 of the file /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce-product-addon/src/Pricing/Engine.php. Error message: Uncaught Error: Class "PPOM\Pricing\WC_Tax" not found in /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce-product-addon/src/Pricing/Engine.php:1400

    Stack trace:

    #0 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce-product-addon/inc/prices.php(64): PPOM\Pricing\Engine::price_cart_fee(Object(WC_Cart))

    #1 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(341): ppom_price_cart_fee(Object(WC_Cart))

    #2 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)

    #3 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/plugin.php(522): WP_Hook->do_action(Array)

    #4 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart.php(2206): do_action('woocommerce_car...', Object(WC_Cart))

    #5 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(276): WC_Cart->calculate_fees()

    #6 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(839): WC_Cart_Totals->get_fees_from_cart()

    #7 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(149): WC_Cart_Totals->calculate_fee_totals()

    #8 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart-totals.php(138): WC_Cart_Totals->calculate()

    #9 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart.php(1543): WC_Cart_Totals->__construct(Object(WC_Cart))

    #10 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce-product-addon/src/WooCommerce/Cart/CartHandler.php(530): WC_Cart->calculate_totals()

    #11 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce-product-addon/inc/woocommerce/cart.php(32): PPOM\WooCommerce\Cart\CartHandler::calculate_totals_from_session(Object(WC_Cart))

    #12 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(341): ppom_calculate_totals_from_session(Object(WC_Cart))

    #13 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters('', Array)

    #14 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/plugin.php(522): WP_Hook->do_action(Array)

    #15 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-content/plugins/woocommerce/includes/class-wc-cart-session.php(287): do_action('woocommerce_car...', Object(WC_Cart))

    #16 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(341): WC_Cart_Session->get_cart_from_session('')

    #17 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)

    #18 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-includes/plugin.php(522): WP_Hook->do_action(Array)

    #19 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-settings.php(793): do_action('wp_loaded')

    #20 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-config.php(93): require_once('/customers/a/e/...')

    #21 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-load.php(50): require_once('/customers/a/e/...')

    #22 /customers/a/e/2/CLIENTS-URL/httpd.www/wp-admin/admin-ajax.php(22): require_once('/customers/a/e/...')

    #23 {main}

     thrown
    Plugin Support Poonam Namdev

    (@poonam9)

    Hi @bluesapphiremedia,

    Thank you for sharing the error.

    We’ve identified the problem and have already escalated it to our development team. They are currently working on a fix, which is expected to be included in the next plugin update.

    In the meantime, as a temporary workaround, you can roll back the plugin to the previous version, where this issue is not present.

    We apologize for the inconvenience and appreciate your patience while we work on resolving this.

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

You must be logged in to reply to this topic.