Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Simon Campbell 25 posts 347 karma points
    Mar 09, 2020 @ 17:21
    Simon Campbell
    0

    Storage Not Working - Labels Reversed

    I have three Formulate forms on a site - one of them stores data as expected, however the other two don't. I can see the POST happen in the inspector (with a 200 code), but nothing gets stored in the DB.

    I don't have any other handlers on these forms - just wanting to store to DB.

    Not sure if it's relevant, but the form that is working was created on my dev machine and uploaded. The two that aren't working were created on the live server.

    Another separate issue is that I just upgraded to 3.2.1 (to see if it fixed the above) and now all my forms have the labels after the control! Any idea what could be causing that?

    Thanks for any help.

  • Nicholas Westby 2045 posts 7032 karma points c-trib
    Mar 09, 2020 @ 17:25
    Nicholas Westby
    100

    The reversed labels are intentional. See the "Label Order" section of this page: https://github.com/rhythmagency/formulate/releases/tag/v3.2.1

    There are two approaches to get the labels in the correct order (one is with CSS, and one is with JavaScript).

    I am not sure why it wouldn't be storing in the database, unless a validation might be preventing if from doing so. The latest release of Formulate should include some JSON in the response for the POST request if there is a validation error.

    Also, be sure the "Store" handler exists on the form. And be sure it is the first handler on the form, as order is important (e.g., a failed email handler might prevent the store data handler from working).

    Another thing to look into would be if there are any special types of fields on that form (e.g., a Recaptcha).

  • Simon Campbell 25 posts 347 karma points
    Mar 10, 2020 @ 08:44
    Simon Campbell
    0

    Thanks Nicholas; have used the CSS solution to fix labels.

    Turns out that the person that made the two forms that weren't working (the client built them), had marked the submit button as required, which of course makes no sense, but it made the validation fail. Maybe that is a feature that should be added - I don't think any kind of validation should be able to be applied to buttons??

    Many thanks!

Please Sign in or register to post replies

Write your reply to:

Draft