• Resolved riios

    (@riios)


    Hello,

    I’m having a problem with my sites form. I have this plugins installed that are giving me this problem: Contact Form 7, Contact Form 7 Conditional Fields, and Contact Form 7 Multi-Step Forms.

    This is the console error:
    jquery.js:4
    POST https://mriios.com/easyas123/wp-json/contact-form-7/v1/contact-forms/6/feedback 500

    The thing is, I currently have a lot of options in my conditional fields (all of the options are in the first drop-down). I can solve the problem if I only leave a couple of groups, but I do need to have a lot of them. Another way to solve the problem without deleting groups, is deactivating Contact Form 7 Multi-Step Forms, but I also need this plugin.

    I’ve tried increasing memory limit, disabling CF7 JS (redirects to an error 500), .htaccess edit, reset permalinks, disabling other plugins, checked file permissions, and maybe some other things that didn’t work.

    Hopefully somebody could help. Thanks in advance!

    • This topic was modified 6 years, 9 months ago by riios.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Getting the same error but with only one group of conditional fields. Seems like there is a conflict between recent CF7 update. Be great to have some feedback from the plugin author.

    Thread Starter riios

    (@riios)

    Based on your reply, I rolled back CF7 to 5.1 and 4.9.2 and still didn’t work. Hopefully someone will get back to us soon.

    Thread Starter riios

    (@riios)

    Meh, went ahead and did it manually with JS. Good luck!

    Plugin Author Jules Colle

    (@jules-colle)

    The CF plugin is not recommended if you are using more than 100 conditions. In that case it makes more sense to implement a custom solution with javascript anyway, because the conditions probably follow some kind of system. A good example of when NOT to use conditional fields plugin is if you are implementing some kind of tree with 3 or more select fields, where the possible values of a select field depend on the selected value of the previous select fields.. or “cascading dropdown lists”, as I like to call them https://bdwm.be/how-to-create-dynamically-populated-cascading-dropdown-lists-for-contact-form-7/
    So yes, you did well implementing your own JS solution to this problem.

    That being said, I’m working on an update that only saves and parses the export version of the conditions, which means that, in theory, you should be able to add unlimited conditions without compromising performance too much.

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

The topic ‘Form doesn’t send, console log error’ is closed to new replies.