Fatal Error and 200: parsererror

  • Resolved mateapetr

    (@mateapetr)


    2 years, 5 months ago

    Going to the settings there should be a sample of the invoice on the right site but I just get this message:

    200: parsererror

    Also when going to orders and creating the invoice the invoice looks all over the place with an error message saying:

    Fatal error: Argument 1 passed to WC_Payments_Explicit_Price_Formatter::get_explicit_price() must be of the type string, null given, called in /jiutopia.com/wp-includes/class-wp-hook.php on line 309

    jiutopia.com/wp-content/plugins/woocommerce-payments/includes/class-wc-payments-explicit-price-formatter.php (128)

    #0 /jiutopia.com/wp-includes/class-wp-hook.php(309): WC_Payments_Explicit_Price_Formatter::get_explicit_price(NULL, Object(Automattic\WooCommerce\Admin\Overrides\Order))
    #1 /jiutopia.com/wp-includes/plugin.php(191): WP_Hook->apply_filters(NULL, Array)
    #2 /jiutopia.com/wp-content/plugins/woocommerce/includes/class-wc-order.php(196): apply_filters(‘woocommerce_get…’, ‘`

    Thankful for any help!

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

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Contributor Yordan Soares

    (@yordansoares)

    Hi @mateapetr,

    It seems that this is related with WooCommerce Payments. Are you using the last release, that today is v4.2.0? You can check this under Plugins > Installed plugins.

    Thread Starter mateapetr

    (@mateapetr)

    Hi Yordan,

    yes, it’s the last release. Payments are working fine. Any idea on how to fix the invoices?

    Plugin Contributor Yordan Soares

    (@yordansoares)

    Please go to WooCommerce > Status > System Status, click on Get system report, then click on Copy for support, paste it on https://pastebin.com/ (set a paste expiration for one week, just in case), and finally paste the pastebin.com link in your reply here.

    Thread Starter mateapetr

    (@mateapetr)

    https://pastebin.com/42F85MTA

    There you go

    Plugin Contributor Ewout

    (@pomegranate)

    Are you using the default “Simple” template? Is this happening to all orders or just specific ones? It looks like something is trying to print an empty price in the invoice and WooCommerce payment cannot handle the way it’s being passed.

    Thread Starter mateapetr

    (@mateapetr)

    Yes I’m using the simple template. It is happening with all orders.

    I’m using plugins: tickera, Deposit payment and custom product fields with prices if choosen with options. Maybe the product fields are making this problem? I tried to deactivate this plugin but nothing changed.

    Plugin Contributor Yordan Soares

    (@yordansoares)

    Did you try to create a new test order after disabling the deposit payment and custom product plugin you mentioned, and then check if the invoice opens correctly?

    Thread Starter mateapetr

    (@mateapetr)

    Yes I have tried it and nothing changed

    Plugin Contributor Yordan Soares

    (@yordansoares)

    Could you please try disabling all your active plugins, except WooCommerce, WooCommerce Payments, and WooCommerce PDF Invoices & Packing Slips and try to open an invoice? If the PDF opens correctly, try activating a plugin at a time, open the invoice on each plugin activation, to check if the invoice still opens correctly, and repeat the process with each plugin. That way, you should find the plugin that is causing the issue.

    Let me know if you find the “culprit”!

    Thread Starter mateapetr

    (@mateapetr)

    I found the culprit. It was the Sellkit Plugin. I deleted it as I don’t use it anyway. Thank you a lot!

    Plugin Contributor Yordan Soares

    (@yordansoares)

    I’m glad to hear that you found the plugin that was causing the issue!

    If you don’t mind and have the time, do you think you could leave us a review?

    Thanks in advance and all the best with your store!

    Thread Starter mateapetr

    (@mateapetr)

    I’ll do ??

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fatal Error and 200: parsererror’ is closed to new replies.