Deftform Changelog

Today's update includes 2 bug fixes and new fonts.

We resolved an issue in Google Chrome where interacting with a conditional single choice (radio) or multiple choice (checkbox) field would cause the form to automatically scroll to the top of the page.

We also resolved a custom CSS rendering issue where characters such as `>` were incorrectly converted to their HTML entities, which prevented the applied CSS from functioning as intended.

Additionally, we added two new fonts: Inclusive Sans and Literata.

Today's update is mainly a maintenance update with minor bug fixes and improvements – nothing major.

We also updated the API endpoint /api/v1/responses/{formID} to better distinguish between complete and incomplete submissions.

We added a new is_incomplete attribute to the response, which is either true or false. You can optionally filter the responses and append ?incomplete=false or ?incomplete=true to the endpoint URL to get a filtered response. The change/addition is documented here.

Of course, this only makes sense when the "Track incomplete submissions" toggle is active within the form settings. If it's disabled, is_incomplete will always be false.

Today we released a maintenance update and also a few fixes and improvements. The most notable are mentioned below.

Conditional fields no longer stick around after changing an answer

We fixed a bug affecting forms with chained conditional logic (where a conditional field reveals another field, which reveals another, and so on). Previously, changing an earlier answer could leave a stale field on screen — so both the old and new conditional fields showed at the same time.

Now, when a field is hidden by a selection, any fields that depended on it are hidden too, and their values are no longer saved with the submission.

Multi-page progress bar now shows your position

The progress bar on multi-page forms now reflects which page you're on, rather than tracking completed fields. On landing, you'll see the bar partially filled (e.g. step 1 of 3), giving an immediate sense of how long the form is and how many pages remain — filling completely on the final page.

We also fixed an edge case where pages hidden by conditional logic could throw off the progress calculation; the bar now always matches your actual position through the form.

Form duplication now includes field conditions

Duplicating a form now copies conditional logic along with its fields. Previously, conditions were dropped during duplication, so any fields configured to show/hide based on another field's value lost that behavior in the copy.

Conditions are now remapped to point at the newly created fields, so conditional visibility works immediately in the duplicated form — no need to reconfigure it by hand.

Today's update includes a new "Address" field and some subtle improvements.

New "Address" element

It's now possible to add an address element to your form, which will generate various address-based fields like "Street Address," "City," "Zip Code," and more.

You can enable and disable fields individually to display only the ones important for your needs. Additionally, you can enable autocomplete, allowing visitors to search for their address and have the fields auto-filled.

The new "Address" element is documented here.

Improvements

We also implemented a few minor improvements in the backend. For example, the "Element" selector, which is shown when adding a new field or element to a form, has been restructured.

At some point, we plan to add a search feature as well.

Additionally, we improved the PDF export feature. It will now respect the widths you set for each field. Before the change, all fields in the PDF export were placed in a new row, even when your layout had different sizes for individual fields, such as a 50/50 layout.

Today, we shipped an update to improve accessibility on public-facing forms. We followed general guidelines and best practices and ran tests through multiple tools to ensure no critical issues were left.

Additionally, as a form admin, you now have the ability to add various aria-* attributes such as aria-label, aria-describedby, and more. New field options were added to the general form settings, as well as to each individual field setting.

Please let us know if there was any oversight on our end, and we will gladly make it right.

Four days ago, one of our CDN providers was experiencing DNS issues, see here: https://status.bunny.net/incidents/j1syhng2crfy

This was causing an issue with the SSL certificate for the CDN URL we were using. We reported the issue with our CDN domain shortly after. Their suggested fix was to re-issue the SSL certificate.

Unfortunately, some of our customers still reported issues with files using the CDN domain. Because of that, we now switched the domain from df-cdn.com to userdata.deftform.com, which should fix the issue as the "userdata" domain is managed by Cloudflare.

Sorry again for the inconvenience.

Today, we released a minor update to further improve our AI-assisted form builder. First, we set a limit of 20,000 characters for the prompt to ensure a reasonable response time. We also increased the timeout window allowed for the AI to respond. Additionally, in case a request still fails, we have added an "Edit Prompt" button. This way, you're not stuck if the first request fails.

Missing images and SSL error

In the past two days, some customers experienced issues with uploaded images not being displayed when viewing forms. This issue was likely related to an incident with one of our CDN providers. Resolving the issue may have taken longer due to DNS change propagation. We have issued a new SSL certificate for the CDN domain and hope this is now resolved for all our customers.

Sorry for the inconvenience.

Today's update includes maintenance, fixes and improvements.

New options for phone field

The phone field has been updated with additional options. It is now possible to disable the automatic country lookup. This was a big request from privacy concerned customers as a visitor's IP address is used to determine the location and pre-select the phone country dropdown.

Additionally, it is now possible to set a default country by specifying its ISO2 code, e.g. "us" for the United States, or "de" for Germany. You can now also define a list of allowed countries. For example, you can enter "de, fr, es" and the country selection will only show Germany, France and Spain.

Fix for custom ALTCHA label

We fixed an issue where custom texts for ALTCHA protection weren't correctly applied and the default english versions "I'm not a robot" and "Verified" were used. If you defined a custom text in the workspace settings, it will now show correctly again. Thanks for reporting.

In addition to the mentioned updates, we fixed a couple of smaller bugs and updated the underlying software to their latest version.

Today's update is mostly a maintenance update but we also fixed and improved a few things.

Fixes

• ALTCHA captcha does not have a white background by default anymore
• Fixed an issue that sometimes occurred when deleting a domain
  
• Fixed a z-index issue that prevented people from deleting their accounts

In addition to upgrading the underlying software and fixes, we added a theme option for the Turnstile captcha. By default, "auto" is used, using the viewers' OS preference. You can also force "white" or "dark" mode.

We also added a new font called "Be Vietnam Pro" that can be used for custom styles.

Today, we released a feature that many of our customers were eagerly awaiting: the ability to track incomplete submissions.

Within the form settings, administrators can now find an option to "Track incomplete submissions". This feature is disabled by default to prevent clutter, but it can be enabled on a per-form basis. Incomplete submissions are displayed as a yellow line in the "Responses" view.

Minor UI and UX improvements

We also optimized a few smaller things across the backend area. For example, the button to add a new element to a form is more prominent. It's also a bit more clearer (hopefully) what to click to contact support.

Additionally, if you are selling products via Stripe, we now fetch product images and display them on the form. To synchronize these images, simply save your form settings once with "Enable form checkout" active.

Today, we released a quick fix for our ALTCHA captcha solution. We've received several reports indicating that the verification checkbox was not displaying correctly, preventing respondents from submitting a form.

This issue only occurred in forms that had "ALTCHA" set for CAPTCHA protection, and oddly enough, it wasn't an issue in every browser.

Sorry for the inconvenience and thanks for reporting.

Just a small update today to let you know that we have added support for additional fields that can be used as context in emails and on "Thank You" pages.

The newly supported fields are:

• Single Choice
• Dropdown
• Country

We updated the documentation to reflect these additional fields.