codimex
Forum Replies Created
-
Thank goodness! I wasn’t crazy!!! YEIIIHHH!!! Looking forward the magical update that will solve all these issues. Thank you! Best regards, too!
Hi again, Adam and WPMU Team!
Thank you for reporting the first issue. Hope it’s fixed soon! 🙂
About the second issue, I’ve performed several tests with the same result. Let me illustrate with screenshots:
1) First, I set all the conditionals as you asked. This link contains the exported form, and you can see how conditionals are set in this screenshot.
2) The first scenario works OK (i.e, when datepicker only conditions one field). This is a screenshot the frontend submission and this is a screenshot of the backend recorded values.
3) The second scenario has the reported error: no values are recorded when a datepicker conditions two fields via “Day is”/”Day is not” conditional rule. This is a screenshot of the frontend submission and this is a screenshot of the backend NOT recorded values.
Plus, the two select fields (conditioned if the datepicker is Saturday or Sunday) are shown if you run the form on a different day than Saturday or Sunday. Trying to set the datepicker default date to “None” definitely crashes the datepicker and the select fields.
Thank you for all your efforts on this. I think we’re arriving at something. Forminator is now awesome, but once this details are fixed, it will be unbeatable.
- This reply was modified 6 years, 3 months ago by codimex. Reason: Typo
I’m facing this problem, too, but with other hidden-by-conditional required fields. Hope the WPMU Team fix it, soon!
Hi Adam! D*mn, you’re right! Sorry for the inconvenience, this is the form I’ve been testing out. :/ Problems I find:
-The summary html field displays hidden-by-conditional fields tags. It would be nice that hidden-by-conditional fields are not displayed when fetched via magic tag to avoid creating one HTML summary field per case.
-When a date field is conditioning two other fields (for example, when you select Saturday or Sunday), they are displayed in the submitted email, but not in the submission database tab.
I don’t know if both issues are related, or if it just happens to me (I followed your “Getting Support Flowchart” and it really looks like it’s not an expected outcome). Anyway, I really appreciate your readiness to help with this issue!
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!
Hi. I know that option, and I’m using each field tag separately, instead of the {all-fields} tag. That’s not the problem. It seems that, in some case scenarios (especially when the “Day is” conditional is activated), the field value is not recorded in the database or displayed in the email.
I’ve uploaded a new form test to make myself clerarer here. Would you be so kind as to test it on your end? Just submit the form with the two possibilities and compare the submissions on the “Submissions” page.
No plugin conflict on my end, BTW. Thank you!
Just to elaborate a little more: some hidden field values (hidden by conditionals) are displayed as well in the email notification. Is it possible just to pass ONLY those fields’ values the user sees, and not all of them, excluding the hidden ones?
Thank you!
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!
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!
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!!!
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!
Hi again. I expected that yesterday’s update, as you anticipated, could fix the problem, but it didn’t. Any plans to have this fixed? Thank you!
After running the basic “deactivation plugin test”, in my case, this error was caused my a conflicting plugin. I deactivated and deleted it and this error is not ocurring anymore. Thank you WPMU Team for giving me the hint in another post!
- This reply was modified 6 years, 4 months ago by codimex. Reason: typo
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?
Hi! Thank you for your detailed help! I really appreciate this! Indeed, it was a plugin conflict. I didn’t see that coming. How could I make that rookie mistake! :”( Luckily it was caused by an expendable plugin, so I proceeded to deactivate it and delete it, and now everything seems to work fine. Let me rate you with five stars for this. Thank you sooo much!