Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter lircabin

    (@lircabin)

    oh, that’s interesting! I will look fix this too. Thanks for the debugging info!

    You are welcome!

    Thanks for the GitHub Repo! gonna add a watch over there!
    Gonna mark this as resolved, thanks for all the info and support @aurovrata !

    Thread Starter lircabin

    (@lircabin)

    the trac repo is reflecting the file changes, you need only this one to get the update, in case you’re in a hurry.

    @aurovrata
    Awesome! I did update it and I tried it out. It does get all of the fields now.
    I haven’t had the time to go through the whole logic and code of the plugin as of yet. But if the dynamic_select is required (dynamic_select*) the validation used in the plugin doesn’t work and returns the message “The field is required” even if the user has selected options. I traced it back to about line 1147 in the “public/class-cf7-grid-layout-public”.
    There’s probably a more elegant solution for this but for me, at the moment: adding a check that if the filed type is dynamic_select* to validate as checkbox* seemed to work for me as the multiple select has essentially the same data structure as a checkbox.

    Thread Starter lircabin

    (@lircabin)

    released v3.3.1 with the multiple select fixed.

    Wow that was quick! Thank you very much

    so apparenlty the repo has an issue and the plugin update is not showing up on the front-end. Do you see it reflected in your dashboard?

    Yes! It didn’t show it yet! Will update it as soon as it does and give it a go!

    Thanks for the concern! Yes, things are really bad right now over here but coding all day has helped.

    Hope you are well over there too!

    Thread Starter lircabin

    (@lircabin)

    However, in the latest version of the plugin, you can now filter individual mail tags (see screenshot #23)

    Oh! I didn’t realize this would work. It’s a good fix for the moment.

    Thanks for this awesome plugin btw!

    • This reply was modified 5 years, 11 months ago by lircabin.

    To see this error, the integration for google recaptcha must be on.
    The error @anthony377 is mentioning is the shown when you activate the integration with google’s recaptcha.
    They all point to google’s domain. And also some of the domains of the cookies are for http and not https google domain.
    So I don’t believe is a problem with the plugin itself.

    • This reply was modified 6 years, 4 months ago by lircabin.
Viewing 5 replies - 1 through 5 (of 5 total)