Support » Plugin: Forminator - Contact Form, Payment Form & Custom Form Builder » Bug report? “Day is” condition involving date fields crashes fields

  • Resolved codimex

    (@codimex)


    Hi again. Just a quick post to let you know that when setting a rule in any field, involving a date field, the “Day is” / “Day is not” rule crashes the datepicker itself and the dropdowns. Thank you and keep up with the good job!

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Adam – WPMU DEV Support

    (@wpmudev-support8)

    Hi @codimex

    I hope you’re doing fine today!

    I’ve also tested this and, I’m afraid, it seems to be the same as with the other issue (with “form section”) as I couldn’t replicate that in any way.

    I think that now even more a full conflict test would be essential for further troubleshooting (so disabling all the plugins but Forminator and then enabling then one-by-one after each one checking for the issue) as it would help identify the source of the conflict that’s causing it.

    Would you conduct such test, please, and let us know about results?

    Kind regards,
    Adam

    codimex

    (@codimex)

    Hi again! Thank you for your readiness to help! Unfortunately, deactivating the conflicting plugin of the other ticket doesn’t solve this problem. The datepicker doesn’t work anymore (it becomes a text field) and the dropdowns become buggy.

    Also, setting a “Month is” condition doesn’t display the list of months. In the other hand, setting “Month is not” condition does display the list of months. Can you also check this while I perform further tests?

    Plugin Support Jonathan – WPMU DEV Support

    (@wpmudev-support9)

    Hello @codimex

    I trust you’re doing well!

    I’ve tested it on my end and could not replicate this issue. Would you please export and share the form with us so we could have a closer look at it?

    To export the form please go to Forminator > Click on settings icon > Export. Please see this screenshot:
    https://monosnap.com/file/MA99ecEw47SwnBmWWvdnb6SwHeFpxs

    Upload the export file to a DropBox or GoogleDrive and share a download link with us.

    Looking forward to your reply!

    Cheers,
    Nastia

    codimex

    (@codimex)

    Hi again! I’ve uploaded here a test form with the issue. These are the issues I find:

    1) When I set “Day is” / “Day is not” involving the date field, the datepicker disappears, the date field becomes a sort of text-field and the dropdown becomes buggy (you can select an option, but it changes the format, as if the bootstrap format had disappeared)

    2) Again, in the visibility tab, setting a “Month is” condition doesn’t allow you to select a month (no list of months appear). On the other hand, selectgin “Month is not” does allow you that (the list of months do appear).

    Thank you!

    Plugin Support Dimitris – WPMU DEV Support

    (@wpmudev-support6)

    Hello @codimex

    1) I can’t replicate this, please check the following screencast in case I’m missing something. Keep in mind that the testing site was updated and using only the Forminator plugin and the TwentyTwenty theme.
    https://monosnap.com/file/QaS0wPJgv7Tg8YSf92cVzXwYURfz0A

    2) I could only replicate the “Month is” part
    https://monosnap.com/file/ihXUWwip1OYONXnB8TrhbNPTnGdxkd
    and I’m reporting this to our devs.
    “Month is not” brings me a dropdown with months that works well.

    Is there a testing/staging site that you could also check that?
    Please advise!

    Thank you,
    Dimitris

    Hi again. Sorry for the late response. Thank you for reporting the “Month is” issue toh the developers team. As for the first issue, I will perform further tests on my end to find out what am I missing. Thank you again and congratulations again for this amazing plugin!!!

    For those having this issue too, this is what I did to solve it: For some mysterious reason, if you create the datepicker field before the field in which you want to create a datepicker-based condition, it may crash those fields (datepicker, dropdown…) -they look buggy and loose format (as a consequence of a “this.calendar.months[n.getMonth(…)] is undefined” console error). This is why my uploaded example worked, but not my original conflicting form.

    Summing up, I could resolve it by creating every datepicker field after every other fields are created. I know it doesn’t make sense, and there must be a logical explanation, but I tested this in three different brand new forms and the error no longer occurs. :/

    Thank you WPMU Team!

    Plugin Support Dimitris – WPMU DEV Support

    (@wpmudev-support6)

    Hey @codimex

    I appreciate the tests on this. Just so I don’t miss anything, can you export this working form and share it with me here in your next reply?

    Thank you,
    Dimitris

    Sure! Thank you again for digging deeper into this.

    The working form: https://drive.google.com/open?id=1-WjE1HbkzEra5Zn35lINKxw2ctWEcNMI

    The error form: https://drive.google.com/open?id=1UKHSsD4CdvjnK14xk7i7Jks8BcF3vXvN

    Look forward your answer! Have a nice week!

    Plugin Support Jonathan – WPMU DEV Support

    (@wpmudev-support9)

    Hello @codimex

    I hope you are doing well!

    Thank you for sending to us both forms. I could replicate this issue on my end.

    Looks like it is happening when in the Visibility section when ” Show this field if All” is selected. If Any will be selected, the date picket is working well.

    I’ve forwarded this to our developers as a bug.

    Thank you for reporting this issue.

    Have a good day and take care!

    Cheers,
    Nastia

    Hi! Thank you again for reporting this issue. :”) It also looks like date fields crash when you select “None” as a default selected date and other fields have conditionals based on that given date field. Have a nice week!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Bug report? “Day is” condition involving date fields crashes fields’ is closed to new replies.