umbraco / Umbraco.Forms.Issues

Public issue tracker for Umbraco Forms
29 stars 0 forks source link

Missing date value in version 13.1.2 #1209

Closed d-osbeck closed 2 months ago

d-osbeck commented 2 months ago

We have experienced that submissions from forms with a datepicker field does not return a value, it is simply empty. At first, we thought it was a problem with parsing the correct date, depending on what Culture we’re on, but the value is not stored in the database either. We believe this to be a bug with Umbraco Forms 13.1.2, as it is has started occurring recently, and other sites running 13.1.1 does not have the same problems. This also only seems to be a problem in the live environment, because it works as intended on a local environment.

image

AndyButland commented 2 months ago

We have made a change with the last patch release, related to the date picker, looking to resolve this issue: https://github.com/umbraco/Umbraco.Forms.Issues/issues/1200

Could be we have missed something here, but if you are seeing the correct behaviour locally but not in production, that's a little odd.

Could there be some cache related difference in what you see either for the request to the initializing JavaScript file between the two environments? This is at the path /App_Plugins/UmbracoForms/Assets/datepicker.init.js and the setShadow() function was modified.

Would also be interested to know what theme you are using please.

d-osbeck commented 2 months ago

@AndyButland

Thank you.

You're right, it was a caching issue that caused me to see different behaviour locally. After clearing the cache, i am experiencing the same problem on both environments.

We are using a tailwind theme, which is really just the default theme with tailwind classes added. However, after downloading the default theme for the latest version of Umbraco Forms (https://docs.umbraco.com/umbraco-forms/developer/themes) and copying over the tailwind classes, it does look to be working correctly. Date values are no longer empty.

I am unsure what was missing in the old theme to cause the issue.