• Resolved sethaugustus

    (@sethaugustus)


    Hi – Thank you for this excellent plugin.

    I successfully installed ELEX WooCommerce Request a Quote. It was working fine until I added 2 fields to the form. Now when I try to edit the form (by clicking the ‘Quote Form’ tab), it triggers a critical error on the site, and the form no longer appears in the pop-up when I click a ‘View Quote List’ button on a product page.
    I’m wondering how to fix this, and if I can revert back to the basic form. This is the free version.

    Thanks,
    Seth

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

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter sethaugustus

    (@sethaugustus)

    UPDATE: I reverted back to a previous version of the site (before I changed the form fields), and it’s working again. I’m curious to know what I might have done to cause the crash? One thing I neglected to do is change the fields in the template (I hadn’t gotten that far). Could that have caused the plugin to crash?

    Thanks,

    Seth

    Thread Starter sethaugustus

    (@sethaugustus)

    Sorry, I should’ve added the PHP error associated with this crash:


    PHP Fatal error: Uncaught TypeError: Elex\RequestAQuote\FormSetting\Models\FormField::build(): Argument #1 ($attributes) must be of type array, null given, called in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormSettings.php on line 299 and defined in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormField.php:59 Stack trace: #0 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormSettings.php(299): Elex\RequestAQuote\FormSetting\Models\FormField::build(NULL) #1 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/FormSettingController.php(54): Elex\RequestAQuote\FormSetting\Models\FormSettings::build(Array) #2 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/RequestAQuote.php(339): Elex\RequestAQuote\FormSetting\FormSettingController::get_settings() #3 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/RequestAQuote.php(232): Elex\RequestAQuote\RequestAQuote->form_settings_localize_script() #4 /wordpress/core/6.8.1/wp-includes/class-wp-hook.php(324): Elex\RequestAQuote\RequestAQuote->enqueue_scripts(”) #5 /wordpress/core/6.8.1/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #6 /wordpress/core/6.8.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #7 /wordpress/core/6.8.1/wp-settings.php(727): do_action(‘init’) #8 /srv/htdocs/wp-config.php(84): require_once(‘/wordpress/core…’) #9 /wordpress/core/6.8.1/wp-load.php(55): require_once(‘/srv/htdocs/wp-…’) #10 /wordpress/core/6.8.1/wp-admin/admin.php(35): require_once(‘/wordpress/core…’) #11 {main} thrown in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormField.php on line 59

    Plugin Support Akash

    (@akashelex)

    Hello @sethaugustus

    Thank you for reaching out and for sharing the PHP warnings—this information helps diagnose the issue.

    To investigate further and replicate the scenario on our end, could you please provide the following:

    1. A screenshot of the new form fields that are triggering the issue
    2. Details about where exactly the critical error occurs (e.g., during form submission, on a specific page, etc.)
    3. The version numbers of our plugin, WooCommerce, and WordPress are currently installed on your site

    These details will enable us to better understand the situation and work on an appropriate fix.

    Looking forward to your response.

    Thread Starter sethaugustus

    (@sethaugustus)

    Hi Akash,

    Thanks for your reply.

    Here are answers to your questions:

    1. I tried to reproduce the problem and it crashed again, so I can’t provide a screenshot, but I can describe below.
    2. When I go to ‘Customize Quote List and Form’ > ‘Quote Form’ (tab) and try to add a Country field and a Postal Code field, it crashed while I was doing this – and I didn’t even save the changes. I had to restore the database on my site to get back to the pre-crash version.
    3. We’re using Version 2.3.5 (I see that there’s an update to 2.3.6, so this must be recently available)

    I’m going to hold off from making changes or updates to the plugin until I hear back from you.

    Thanks again,
    Seth

    here’s the error from just now:

    PHP Fatal error: Uncaught TypeError: Elex\RequestAQuote\FormSetting\Models\FormField::build(): Argument #1 ($attributes) must be of type array, null given, called in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormSettings.php on line 299 and defined in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormField.php:59 Stack trace: #0 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormSettings.php(299): Elex\RequestAQuote\FormSetting\Models\FormField::build(NULL) #1 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/FormSettingController.php(54): Elex\RequestAQuote\FormSetting\Models\FormSettings::build(Array) #2 /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/Quotelist/QuoteListController.php(481): Elex\RequestAQuote\FormSetting\FormSettingController::get_settings() #3 /wordpress/core/6.8.1/wp-includes/class-wp-hook.php(324): Elex\RequestAQuote\Quotelist\QuoteListController::get_the_quote_list(”) #4 /wordpress/core/6.8.1/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(”, Array) #5 /wordpress/core/6.8.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #6 /wordpress/core/6.8.1/wp-admin/admin-ajax.php(192): do_action(‘wp_ajax_get_the…’) #7 {main} thrown in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/FormSetting/Models/FormField.php on line 59

    Plugin Support Akash

    (@akashelex)

    Hello @sethaugustus

    Thank you for your response.

    I’ve tried to replicate the scenario by creating the country and postal code fields under the quote form on our end using versions 2.3.5 and 2.3.6, but I didn’t encounter any critical errors or PHP warnings.

    https://tinyurl.com/28xylsv6

    No worries — we’ve released an updated version of the plugin that includes a fix based on the PHP warnings you shared. Kindly update the plugin to the latest version and let us know if the issue still persists.

    Thread Starter sethaugustus

    (@sethaugustus)

    Hi Akash,

    I just updated to 2.3.6 and was able to re-configure the form without fatal error(s). I checked th elogs and below are some deprecation warnings.

    Thank you so much for the support, and for fixing the plugin right away! I’ve asked my client to buy the pro version.

    Let me know if there’s any more testing you’d like me to do.

    Cheers,
    Seth


    Deprecated

    Tue, 13 May 2025 21:46:24 UTC

    Kind:plugins

    Name:elex-request-a-quote

    PHP Deprecated: WpFluent\QueryBuilder\QueryBuilderHandler::newQuery(): Implicitly marking parameter $connection as nullable is deprecated, the explicit nullable type must be used instead in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/wp-fluent/src/QueryBuilder/QueryBuilderHandler.php on line 114

    Deprecated

    Tue, 13 May 2025 21:46:21 UTC

    Kind:plugins

    Name:elex-request-a-quote

    PHP Deprecated: WpFluent\Connection::__construct(): Implicitly marking parameter $container as nullable is deprecated, the explicit nullable type must be used instead in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/wp-fluent/src/Connection.php on line 49

    Deprecated

    Tue, 13 May 2025 21:46:21 UTC

    Kind:plugins

    Name:elex-request-a-quote

    PHP Deprecated: WpFluent\QueryBuilder\QueryBuilderHandler::__construct(): Implicitly marking parameter $connection as nullable is deprecated, the explicit nullable type must be used instead in /srv/htdocs/wp-content/plugins/elex-request-a-quote/src/wp-fluent/src/QueryBuilder/QueryBuilderHandler.php on line 59
    Plugin Support Akash

    (@akashelex)

    Hello @sethaugustus

    I am glad that our latest release version has resolved the issue on your site. Sure, we will check the “deprecation warnings” in our next release, but I hope it won’t affect any plugin features and functionality on your site.

    Please consider sharing your valuable feedback on our product review page if you are satisfied with our product and support. Have a nice day!

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

The topic ‘Adding fields to form crashed the plugin’ is closed to new replies.