On my server a metadata refresh populated my albums with the actual release date of the album; it appears that Plex is not longer pulling that information from the “Year” tag in my files, but using their sources for the actual date.
I have not tested manually setting a release date to Jan 1 to see what happens.
edit: I’m using the Plex Music scanner and agent, with “Prefer local metadata” selected.
This is a really annoying bug. I really hope I don’t h have to re-scan my entire music collection to fix this… for something that has a date of: 2022-01-01 if I fix just one day or month to something like 2022-01-02, it will show 2022 instead of 2021… wtf…
Right, the fifth beta of 1.27.0 just released:
Why wait for 1.27.1 and not just include a fix for testing in the current 1.27.0 beta releases? I would love to know what was the decision process for this bug, especially knowing how disruptive it is for some people.
Affirming that this bug is present in 1.26.2.5797, and prevalent across all my music.
Also, Album Artist sorting is absolutely confounding.
I usually don’t install Beta’s but in this case I thought I should for this issue. I installed the latest beta on my Qnap and moved over some new albums. The dates are now showing correctly for 20XX-01-01.
I was going through and updating any new albums that I put in there. However, I know some got past me where it scanned older stuff. Will this eventually correct those dates I am not aware off?
After updating to version 1.27.0.5897, and doing a complete Metadata Refresh on the entire music library, years look to be corrected and properly represented.
I just upgraded to 1.27.0.5897. I use “Prefer local metadata”.
Added a new music album, both in flac and mp3 versions. Date in source files is year only - 2014 in this case. The album under Artist view shows 2013, but Originally Available in album Edit shows 2014-01-01. Changing Originally Available to 2014-01-02 makes the album show as 2014.
This is no different than the previous release’s behavior.
Added another album with 1970 in the source files’ date field. Album in Artist view showed no date at all. Album Edit showed Originally Available as 1969-12-31. Changed Originally Available to 1970-01-01 (not 1970-01-02) and the album’s date in Artist view shows as 1970.
The fix is in the beta…. 1.27.1…… not 1.27.0.
Okay, thank you. There was info from other posts and the release notes for 1.27.0 that made it sound as if it was fixed.
Ok I have updated to 1.27.1.5891 and still seeing this issue.
Year is shown as previous year, when the Originally Available is year-01-01, when you set it to year-01-02 years match, say 2021. But if you change it back to 2021-01-01 the year on the album is shown as 2020.
This happens no matter if the year is 1996 or 2022, etc. … I am in Central timezone.
I had a chance to install the new 1.27.1.5891 beta release, and it seems to be finally fixed for me!
I updated from 1.25.9.5721, refreshed the metatada on a few albums that have a “XXXX-01-01” date in the Originally Available field, and the right year is now displayed for the albums.
@mrjohnpoz, it would be interesting to know why you can still reproduce the issue.
I am not seeing the issue either… However, if you did do a scan on the old version and these files were scanned on the old version and no Metadata refresh, it’s still possible to see the date miss match. I just added a bunch of albums and none of them had the issue… but I did find a couple of older items that were scanned on the older version that still had the issue. I don’t do metadata refreshed all that often.
Can you confirm this album was added with the new build and not scanned with the old one?
No - I was going to try that… I don’t have anything specific to add that is new currently… But let me pull the latest one and do the plex dance on it and see if that fixes.
If that is the case, have any ideas on how to fix on old stuff? BRB after testing.
Ok… I removed an album with date 2021-01-01… Scanned library, it showed as unavailable… Emptied trashed, cleaned bundles…
Put the album back, and still same problem showing year of 2020 vs 2021.
Is there something else I would have to do other than empty trash and clean bundles? I could try optimize db…
edit: ok did the whole process again, and optimized db this time as well… Same thing showing previous year… I am clearly running 1.27.1.5891, I double checked that. Let me find something completely new to add. BRB
edit: Ok added a completely new album, date of 2022-01-01 and it shows up 2021… Never had this album in plex before ever…
@ASiDiE what are you running plex on? Mine is running on synology nas ds918+ the native install from plex for dsm 7, running dsm 7.1 update 2
edit2: here I just validated from the log what version its running
Jun 15, 2022 07:59:44.080 [0x7f7dcbe62b38] INFO - Plex Media Server v1.27.1.5891-c29537f86 - Synology DS918+ x86_64 - build: linux-x86_64 synology-dsm7 - GMT -05:00
Jun 15, 2022 07:59:44.080 [0x7f7dcbe62b38] INFO - Linux version: DSM 7.1.42661-2, language: en-US
I am running on on a QNAP… I download the installs every time. I upgraded from 1.26.2.5797 (Public release) to the 1.27.1.5891 beta… Might be something different there.
I will continue to add new stuff… I check it from being on the album (like your screen shots) and editing them there. I also go in by Band name and then see all the albums and click on each one to check the dates and so far all is working as it should.
I do want to figure this out so nobody has to deal with this again.
I upgraded from 1.27.0.5897
So strange that its working for you… I am always running whatever the latest beta is, I rarely have any issues… And can’t recall the last time I ever had to roll back… But I keep like the last 5 or 6 installs if I ever have to roll back… But just looked oldest copy I have local is 1.27.0.5849
Yea… I would really like to see anyone else respond to this one. I came in late in the game I think but there were several people seeing the issues that posted before. Maybe they don’t install betas but I think this issue needed to be fixed right away.
Anyone else still seeing the issue?
BTW what timezone you in - I think it has something to do with timezones… because if you change to 2nd day vs 1st it uses the correct year.
Maybe they sort of fixed it depending on timezone your in 
And I just happen to be in the wrong time zone
I am in Denver… Mountain Time zone.
