JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.
We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.
Submission Data from Encrypted Form displays incorrect DateTime FormattingAsked by lalaucb on March 03, 2016 at 09:29 AM
My form contains a Date question formatted to be MMDDYYYY. For instance, the date submitted is March 04, 2016). However, the submission email received is displaying the date wrong. It says Date 03.
Please advise. Thank you.
I found I am able to replicate the same issue you are having with the email displayed in differently than what is set on the form field. Thank you for reporting this issue to us. I've sent a bug report about this to our developers so that we can get this problem fixed as soon as possible.
Date Set as MMDDYYYY:
Date Received in Email:
UPDATE: I ended up doing some further tests and I believe I've found the cause of this problem.
I noticed that your form had encryption enabled so I tested this furthermore in a separate test where I found if it's disabled then the form date regardless of the setting is displayed correctly in emails.
However, once the form encryption is enabled or re-enabled it breaks how the date is displayed.
So I've narrowed this down to the fact that either there's a problem with the notification when using encryption or the online version of the notification email when viewing it from an encrypted form might be the other possible cause.
Without Encryption on New Date Formatting Test:
With Encryption on New Date Formatting Test:
My form requires encryption. Are you able to fix the date display in the notification email?
My colleague has reported this issue to our developers. Once this issue is resolved we will inform you via this thread.
Today we released a patch that fixes this bug. Please do inform us if you have any other questions or concerns.