Product Icon

Request a Quote for WooCommerce

Allow your customers to add product(s) to quote basket and ask for price estimation by submitting a customizable quote form.

Error when no price is set

In our case we cannot set prices on products. When no price is set this triggers an error on form submission on class-af-r-f-q-quote.php line 293:

PHP Fatal error: Uncaught TypeError: Unsupported operand types: string

I’ve added a simple fix to detect empty prices and set it to 0, but i guess this should really be fixed by you guys for future updates.

Author

wallmanderco2017

Current Status

Open

Last updated: August 4, 2023

5 comments

Log in to comment on this feature request.

  1. Addify says:
    Product Developer December 20, 2023 6:18 pm

    Hi,

    Hi Len,

    Please reach out to us using following email,
    support @ addify.co

    Thanks,

  2. Len Bradley says:

    Addify, I would create a ticket but “Request a Quote for WooCommerce” does not exist as an option in the Product dropdown. Is there another preferred method of contacting your support team directly?

  3. Addify says:
    Product Developer December 19, 2023 8:05 am

    Hi Len,

    We recommend you to please reach out to our support team since we do plan to release a new version in coming weeks as the extension does not display add to cart button when the price is empty. Please reach out to us using the following link,

    https://woocommerce.com/my-account/create-a-ticket/

    Thanks

  4. Len Bradley says:

    Could we please get this issue fixed? We have a few clients who are affected by this and it’s not a good solution to have to go into the code and hack it every time the plugin is updated. Here’s an easy solution:

    File: /woocommerce-request-a-quote/includes/class-af-r-f-q-quote.php

    Line 192:
    — Replace: $price = $product->get_price();
    — With: $price = ( $product->get_price() ?: ‘0.00’ );

    Line 270:
    — Add: $price = ( $price ?: ‘0.00’ );

  5. Addify says:
    Product Developer August 4, 2023 7:22 am

    Hi,

    Thank you for reaching out and reporting this issue. We have passed it on to the development team to fix this issue in next release.

    Thank you,