The first Caldera Forms update of 2016 — Caldera Forms 1.3.2 is now here. Honestly, you shouldn’t notice anything has changed. This one is all “under the hood.”
This new version has no shiny new features, but we’ve put a lot of effort into improving the reliability of form submissions via AJAX. We’ve also improved how fields are rendered. Validation for multi-page forms — that works better now.
In Caldera Forms 1.3.1, on some, but not all servers using Apache, Caldera Forms AJAX submissions were not working with the “plain” or “ugly” permalinks setting. To fix this, we have done two things. The first is that the URL we use for processing AJAX submission will automatically fallback to using a query-string, instead of a “pretty” URL if pretty permalinks are not enabled. This should fix all issues.
Because nothing is 100%, when using AJAX submissions, if the submission returns a 404 error, Caldera Forms will try again, without using AJAX. This will cause a page refresh, but it will work. This fallback shouldn’t be necessary, but it is there, just in case.
A cool side effect of this is that we know have a filter “caldera_forms_cf_ajax_api_url” which can change the URL AJAX submissions are sent to. This is just another way that advanced developers can make use of Caldera Forms’ awesome front-end to process form data anyway they want.
Caldera Forms 1.3.2 is available now via WordPress.org. For a full list of changes, see the changelog in the Caldera Forms readme, or checkout the 1.3.2 milestone on Github