Date field not saving date correctly when popup calendar is used and date format is hiding the year

[albanycomputers]

Description of the bug

Date field not saving year when display format is set to not show year but popup calendar shows year.

Steps To Reproduce

To reproduce the behavior:

1. Create new Date & Time Format
   

2. Create new content type or edit an existing Date field to use the date format above and popup calendar

3. Enter content with dates... for example 7th of September 2022 and save content

4. Edit the content type and change the date format to "Long date" for example

Actual behavior

Year, while showing in the popup calendar isn't being saved properly.

Expected behavior

I would expect the date to be saved in a UNIX date format and the Date and Time format would display the date as you wish... allowing the correct date to be saved.

Additional information

Add any other information that could help, such as:

• Backdrop CMS version: 1.20.1

[albanycomputers]

When the Date field is then used with Views the date does not show up correctly.

The Term-end date was entered as 2022.

[albanycomputers]

While I am aware that I could change the date format to

To allow the correct date to be entered, I wanted the site owner to see the date as it would be displayed on the site.

[indigoxela]

I'm not sure if I get the problem... actually I'm pretty sure I do not understand the problem. 😉

You do want people to input dates - to save a date it needs a year. Dates without year are impossible. That means they do have to choose a year. How could people select a date, when they don't select a year?

The input format for the popup calendar is not fully configurable. Under the hood it has to be compatible with the js calendar widget (jquery.ui.datepicker).

[albanycomputers]

@indigoxela The end user, or in this case me add content then select the popup calendar and choose the full date, 9th November 2022... once the date has been selected the display then show just the day, date and month. as above.

I first noticed the problem when I display the view of Academic Term as shown below...

The End date was entered as 2022 in the calendar popup when creating the content but in the View it is being shown as 2021...

[albanycomputers]

With some dates the year was also saved as 0000 with the month and day correct.. e.g. 29/05/0000

[indigoxela]

With some dates the year was also saved as 0000

Huh? Can you reproduce that on a vanilla install?

The End date was entered as 2022 in the calendar popup when creating the content but in the View it is being shown as 2021

I belief, what you want (display partial date when inputting) is impossible. But somebody else might want to chime in.

I've just been able to produce a EntityStorageException by using a totally silly input format for the date popup widget, but that's maybe worth another issue.

[albanycomputers]

To give a bit more detail...

The content type is : -

The "Term Date", date entry option as this: -

and the Field settings: -

The "Term Date" display format : -

I'm now entering a new start and end date with the calendar popup and choosing the Tuesday 4th of Jan 2022

to Saturday 26th of March, 2022

and on the view... Term 2 is showing Wednesday 5th January and Monday 27th of March

I'll now change then display for the data entry to a "Long date"

The edit the Term 2 I've just created... and the year has been saved as 0000

[albanycomputers]

The display format should not make any difference to the data saved, it is just a "display" format, not a "save" format.

[albanycomputers]

Many thanks... it also changes the day for example, I entered the 4th of January and after saving it displays the 5th of January.

[indigoxela]

The display format should not make any difference to the data saved

I don't think your problem is about the display format (displayed dates after saving), but your problem is about the input format.
Input means, the date as displayed (cough...) in the little text field, the calendar pops up from.

That's the actual input value. Changing that to some incomplete date format will end up in weird behavior.

[albanycomputers]

Hmm... yes, of course, and the more I've thought about it over the past couple of hours the clearer its behaviour has become.

And because "Dates" are such a complicated thing to display... and for modules to interpret, ambiguities are bound to happen.

I think the thing that "got me" was the [Field Settings] tab having the Granularity of Year, Month and day selected and the popup calendar letting you choose a Year, but the [Date Entry option] doesn't have the Year active and didn't save it.

So when I came to display the Date in a View, the View was doing the best it could with the information it had :-)

So, with taking the above into consideration... I'm sure other people will have similar problems with Dates and the display format...

I know I wouldn't have read the manual lol... but would it be prudent to post a warning on the [Edit] tab and the [Date Entry Options] to something like...

"Beware that only the Date sections specified below in the Date Entry Options will be saved to the record and other modules may interpret the 'empty' parts differently. "

[meghagangadhar13]

I would like to work on this under Openforce 2022