Incorrect date format used for date scanned into library

[travisms 1]

Hi All,

 

I have an issue that I cannot seem to find the cause of.

Certain movies are getting their date added flag set in YYYY-DD-MM format instead of my servers YYYY-MM-DD format which is future dating certain movies.

I presume it is only happening with movies that are added on a day from 1-12 that corresponds to a month hence why I am not seeing it on all movies.

 

Example below:

Date modified in Windows is 2025/08/12 (YYYY-MM-DD) however the NFO file created date added is in YYYY-DD-MM  -   <dateadded>2025-12-08 20:42:16</dateadded>

 

My Library settings are set to Use date scanned into the library - I had this previously set to Use file creation date and had the same issue.

My server settings are set to use the YYYY-MM-DD short date format set.

I tried manually editing the metadata for each of the future dated items via the Web UI however they set themselves back again a while later.

 

Any ideas where I can possible look for the issue or what I can change to fix this ?

 

[Luke 42077]

Hi, what makes you think they are actually future dated? This is probably just the web app display showing them in that format.

[travisms 1]

17 minutes ago, Luke said:

Hi, what makes you think they are actually future dated? This is probably just the web app display showing them in that format.

The others (not with a day from 1-12) display correctly while those in the incorrect format constantly display in front of all the others under Latest Movies as well as repetitively in the daily New Media Report Notifications until that future date has been reached.

Below is an example of a movie added today with the correct YYYY-MM-DD format:

Edited August 27, 2025 by travisms
spelling

[Luke 42077]

OK the issue is your nfo files. Our nfo reading and writing is assuming the added value to be yyyy-MM-dd

[travisms 1]

24 minutes ago, Luke said:

OK the issue is your nfo files. Our nfo reading and writing is assuming the added value to be yyyy-MM-dd

I noticed that it was incorrect in the nfo although set correctly in the plugin.

I only put down the media file and the nfo is auto created afterwards with the incorrect date format - any idea what I can change to prevent this ?

[Luke 42077]

Quote

I noticed that it was incorrect in the nfo although set correctly in the plugin.

Then Emby didn't write the nfo file. Something else did, and Emby Server then imported the contents.

Quote

however they set themselves back again a while later.

This is further evidence that you have something else writing nfo files.

[travisms 1]

@LukeThanks for pointing me in the right direction -  I had a legacy metadata option enabled under Radarr which I assume could be the issue.
I will disable it and monitor to see if that was the issue.  Thanks!