Server Version#: 1.31.3.6868 (Windows x64)
Player Version#: Web 4.104.2, Plex for Windows 1.67.1
This is a minor bug and easily worked around, but thought I’d report it regardless.
When editing an item in the web/desktop clients, there’s validation that blocks everything except [yyy]y-[M]M-[D]D [HH:mm:ss] and a standalone 4-digit year. However, the standalone year case is not handled properly, and instead gets interpreted as, “YYYY seconds after 1970-01-01 00:00:00”. It’s easy enough to fix by manually adding ‘-01-01’, but it seems like that should be done automatically, or at the least the operation should be blocked to prevent unexpected dates from being entered.
I dug into it a bit, and it looks like there is some handling in the web app that transforms “2001” into “2001-01-01” when validating new fields (invalidChangedAttrs), but when Plex actually goes to save the changes, it grabs the original “2001” instead of the modified “2001-01-01”, which then goes into the database as-is, resulting in a new Originally Available date of 1970-01-01.
