conditionals not being saved

  • IT Hertz

    (@it-hertz)


    1 year, 9 months ago

    After clicking the Save button, all conditional settings are wiped when a field value contains spaces.
    For example: “FieldValue” works and settings are retained, but “Field Value” causes all conditionals to be lost (it also deletes the conditionals that do not contain spaces).

    This is a major bug which renders the plugin practically useless for control fields where normal text string values are presented to or desired from the user. Currently, we have to use underscores for everything. Lack of adequate testing here.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    We are extremely sorry for the inconvenience you had. Please accept our sincere apologies. It was quite an unexpected issue.

    We are investigating each and every part of our plugin and trying to figure out the issue.

    Hopefully, we will give you feedback very soon.

    Best wishes,
    Support Team

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    we have fixed the issue and released an update of our plugin. Would you please update the plugin to the latest version?

    Hopefully, it will solve the problem.

    Best wishes,
    Support Team

    Thread Starter IT Hertz

    (@it-hertz)

    1 year, 9 months ago

    Well, it no longer deletes everything, so that’s progress.
    I see you’ve replaced the first space in the value string with an underscore. Ok, but now it nulls out values when a string contains spaces beyond the first one. Strangely, it also adds its own conditionals.

    Example:
    Using UI with spaces and no underscores, text mode shows this: 

    show [groupA] if-[Field_A]-equal-"Test_Value A"
 and-[Field_B]-equal-"Test_Value C"
show [groupB] if-[Field_A]-equal-"Test_Value B"
 and-[Field_C]-equal-"Test_Value D"

    However, this is what happens after Save:

    show [groupA] if-[Field_A]-equal-""
 and-[]-equal-""
 and-[Field_B]-equal-""
 and-[]-equal-""
show [groupB] if-[Field_A]-equal-""
 and-[]-equal-""
 and-[Field_C]-equal-""
 and-[]-equal-""

    The fix is to replace ALL spaces in strings with underscores. When I do this manually e.g., “Test_Value_A_Additional_Text”, they don’t get nulled and no unwanted conditionals are added.
    Fortunately, the plugin ignores input underscores, so entering “Value_A” doesn’t result in “Value__A” but instead “Value_A” as entered.

    Unfortunately, null value conditions are not working:

    show [submit] if-[Field_A]-equal-"Test_Value_A"
 and-[Field_E]-not-equal-""
show [submit] if-[Field_B]-equal-"Test_Value_B"
 and-[Field_E]-not-equal-""

    The above results in the submit button being shown at all times, even when the null condition is met. In this test case, Field_E is a text field, but the same occurs with other field types. The logic isn’t working, whether the field is empty or not, and whether I use equal or not-equal and leave the conditional value null or not.
    I went ahead and put the logic issue in this thread because I don’t know whether it’s related to or caused by the changes you made while trying to fix the space/underscore/null string issue…

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    Thank you so much for your valuable feedback. We are working on it.

    After investigating we found out that we need to change several parts of the plugin to fix the problem properly. So it will take a few days for updating the plugin.

    Hopefully, we will fix the problem and update the plugin soon.

    Best wishes,
    Support Team

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    First of all, We appreciate your feedback, and thank you so much for sharing the problem with us.

    However, we’ve fixed the problem. Please update the plugin in the latest version.
    Hopefully, you are able to input any kind of value in the condition field now.

    Whether the filed’s value contains multiple spaces, underscore, or null, you shouldn’t face any problem.

    Best wishes,
    Support Team

    • This reply was modified 1 year, 9 months ago by HT Plugins.
    Thread Starter IT Hertz

    (@it-hertz)

    1 year, 9 months ago

    Hi,

    Sorry for the delayed response. Got busy with other things.
    Yes, that took care of the null string issues. Thanks for getting that done so quickly.

    However, your plugin isn’t playing nice with a signature field on my form, so for now, I’ve had to go back to using the Conditional Fields for Contact Form 7.

    In case you’re wondering, I offer the user 2 ways to attach a signature: stylus/finger drawing box and upload existing image file. One hides when the other is selected via toggle buttons, and the submit button shows only after a signature has been attached.
    A goal is to clear data from one method when the user selects the other method, for 2 reasons: so that only one attachment will be saved to the database, and to avoid extra button/step forcing the user to manually empty one before being allowed to access the other.

    I’m still having trouble clearing the signature field and showing the submit button with Jules’ plugin, and the submit button doesn’t show when the box is drawn in. As a temp workaround, I added an “Accept” button that brings up the submit button when the user is satisfied with their drawn signature. It’s buggy, showing the submit button when ANY form field is clicked on. argh! This form is kicking my butt.

    At any rate, it would be helpful if your plugin provided a clear_on_hide function like Jules’ plugin, but even if yours had that, it still isn’t working with my toggled hiding of draw box vs. upload form, which would require deeper troubleshooting.

    I realize this is a compatibility issue with the signature plugins that I’ve been trying and it’s outside the scope of support for your plugin. I’ll see what the signature plugin authors have to say about it.

    I guess you can consider this lengthy reply to be at least a clear_on_hide feature request. 🙂

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    Thanks for the reply.
    Actually, we need a little more clarification from you.
    Does the clear_on_hide function only apply to those fields which are conditionally hidden or shown?

    OR

    It would be great if you could contact us at https://hasthemes.com/contact-us/
    Our support team would love to assist you with this.

    Best Regards,
    HT Plugins

    Thread Starter IT Hertz

    (@it-hertz)

    1 year, 9 months ago

    Well, it applies to groups instead of individual fields, so the attribute goes in the group tag, but yes, clear_on_hide resets all field data within the group when that group is hidden from view via conditional rule.

    Of course, it could be applied to individual fields, if said fields are in their own, separate groups.

    When the clear_on_hide group is next unhidden, the fields within the group will be empty (or whatever their default is).

    This has several advantages:

    • It spares the user from having to manually empty fields if they change their mind and decide to hide whole sections from view.
    • It helps ensure that only the data actually desired to be sent by the user is submitted.
    • Because of #2 above, it spares the admin from backend confusion and potentially erroneously acting on incorrect/unwanted data saved to the database, by eliminating data the user didn’t actually intend to submit (and assuming the user forgets to or is simply too lazy to go back and unhide and empty all unwanted fields).
    • Using my signature/upload option case as an example, it helps when the form designer needs to toggle control/input sections and needs to clear one section when the user selects a different set of controls.

    See this for more details on what his plugin does: clear_on_hide docs

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    Thanks for the reply with a brief description.
    We have taken it into our consideration.
    Hopefully, we release a new update of the plugin in the next couple of days.

    Best Regards,
    HT Plugins

    Plugin Author HT Plugins

    (@htplugins)

    1 year, 9 months ago

    Hello @it-hertz

    We have added the clear_on_hide option for the conditional field group and also released a new update of our plugin. Please update the plugin in the latest version.

    Hopefully, You will have got your expected result.

    Best Regards,
    HT Plugins

    • This reply was modified 1 year, 9 months ago by HT Plugins.
Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘conditionals not being saved’ is closed to new replies.