I can confirm. Noticed the same error right now.
Server Version: 1.26.0.5715
This will be fixed in PMS 1.26.1
I have tested an alpha version and it works again for me.
7 Likes
Thanks so much! Have you also tested that a date modified before 1.26.0.5715 doesn’t get changed one day earlier after updating like previously discussed?
1 Like
Any idea when that might be available, in the beta channel? Plex Pass subscriber - I normally don’t have an real issues running whatever the latest and greatest code… But this issue bothersome, not a show stopper or anything - stuff is still plays, and everything I do for sure works - but it annoying with date thing for sure.
1 Like
I would like to know when the new update will be released. Not only must it stop the “1969-12-31” error, but it also needs to RESTORE all the dates that were previously correct but have been moved back one day. Please fix this as soon as possible and take steps to ensure bugs like that don’t occur in future updates. Thanks.
1 Like
Is there an ETA?
1 Like
Bug confirmed.
Server Version: 1.26.0.5715
1 Like
This wrong airdate error still persists. I got fed up with waiting so I took matters into my own hands. I decided to completely uninstall the terrible bugged version of PMS 1.26.0 with Revo Uninstaller. I then scanned for leftovers with that program and deleted everything that came up in the results, then I rebooted my computer.
Next I downloaded the previous installer version which was “PMS 1.25.8.5663” from a site that has old versions of Plex installers uploaded.
After doing this and setting up my server on the downgraded version of Plex ALL of the airdates have been restored to their original and correct dates. The only dates that were still incorrect were the dates that I tried to edit manually while running 1.26.0 and wouldn’t save because of the bad 1.26.0 PMS glitch.
So if you are sick and tired of this glitch and you don’t feel like waiting weeks or longer for Plex to finally fix this in their next update then simply do what I just did and everything will be fine again. Just remember to go back to the dates that you manually tried to edit during the glitch and fix those ones, all the others will be restored properly.
I can’t believe I had to jump through all of these hoops in order to fix a huge error that Plex created themselves due to lack of awareness of what they were doing, which is equal to sheer incompetence. The Plex team needs to do much better in the future to avoid messes like this occurring again. I hope this can be of some help to others out there as frustrated with this situation as I was.
Such drama.
2 Likes
I mean, the bug sucks but at least it doesn’t destroy existing data… unlike the metadata provider upgrade that blew away all of my “locked” overrides. Does the lock function even do anything?
1 Like
All the lock function does is provide a false sense of security. It’s worthless. Many times over the years fields that I’ve locked have reverted without my permission after library updates or server updates, it’s completely pointless to lock anything and expect it to remain exactly as you left it next time you check.
Why are you not supposed to use a third party uninstaller like Revo Uninstaller? It did the job and worked just fine. Back in 2018 I had an issue where I couldn’t get Plex to install, the normal program uninstaller would not remove it completely. So whenever I downloaded a fresh copy of the installer and tried to install it again it would never complete.
I actually got advice about this problem from someone here who told me to install Revo and use that, and it worked! If not for Revo I’d never have gotten my Plex up and running again. So for anyone to say ‘don’t use software like Revo’ is ridiculous. Especially since the people who wrote that on the help page are also the ones who created this bad PMS 1.26.0 update in the first place!
1 Like
I’m not suggesting to never use those things. They are sometimes useful. (They are often oversold/unnecessary/snake oil - Revo is better than many.)
When merely downgrading, one typically WANTS to preserve settings.
Using an uninstaller-cleaner is likely to erase settings, require the server to be claimed again, and possibly remove the Library and metadata database.
An unnecessary step for a downgrade, with potentially harmful side effects.
Not a judgment on the tool. Drain cleaner is great when it’s necessary.
Lock is also a flag in the database. The agents are supposed to observe it.
I saw this complaint a lot when the new agents were made default. Especially with posters, but I was never sure if they were manually chosen posters, or if they were just changed to different default posters.
I haven’t been able to reproduce Plex ignoring and overwriting locked fields. Can you?
From personal experience, the overwrites do not occur as frequently in my environment lately. The many actions that would trigger an overwrite before do not trigger an overwrite now. However, Plex upgrades seem to trigger overwrites often. The most notable event was when a metadata provider update affected audio files, music.
I spent over a year ripping and uploading CDs, then manually editing any incorrect data. There are more than 1,000 entries in my library. When the update occurred, I noticed Japanese text and knew my metadata was messed up. Sure enough, other English releases were also reflecting the metadata provider entries.
I was… gently pushed to perform free labor for the benefit of MusicBrainz and their users. A single correction took a week to implement and to be reflected within my Plex library. This was after I took the time to register to MusicBrainz and learn the platform rules. With an unknown number of problems and over 1,000 entries to review, I gave up. I have a stack of new albums that I want to add to the library, purchased before the incident event. I won’t touch them now. I feel uneasy and the stack of CDs worth over $300USD is painful to look at.
If you are going to look anywhere, I would suggest you focus on the software upgrade process. However, I doubt you nor the Plex Staff will resolve the deeper issue. I paid an absurd amount of money converting my family to Plex. I might be a minority here, but the metadata and organization is what won me over against the other hosting solutions. Plex has a trend of not honoring metadata. When this issue is fixed, another will spring up. The priorities at Plex will need to change to truly resolve metadata issues.
I find that Discourse is an interesting selection to connect the Plex community. The free Discourse software has not once failed to protect my data nor the data of my clients. I have experience with Discourse since the days before Major Version 1. I have upgraded a Discourse environment running a version prior to Major Version 1 to a Major Version 2 deployment. No data was lost. This showcases priority. I find it ironic that this conversation about Plex metadata is facilitated by Discourse.
1 Like
Just to be clear from my experience, after using Revo Uninstaller I did have to claim my server again, but that was painless. It did NOT remove or mess up my libraries nor did it remove or mess up any of my metadata in the Plex metadata folder. Which is clearly separate from the normal program installed Plex folder. Revo messed up nothing this time nor back in 2018 when I used Revo to completely remove Plex when I couldn’t uninstall it properly normally. It’s a very effective program that I would recommend to anyone who is having trouble removing a program that doesn’t want to uninstall normally for whatever reason.
1 Like
What’s funny about that is that if you didn’t have to reconfigure or re-claim Plex after using Revo, that means Revo is a poor uninstaller - it left things behind!
I haven’t used it in a long while. I assume it still has various “levels” of cleaning. 
Version 1.26.1.5762 for Plex Pass subscribers was released some time overnight. I just upgraded and did some date edits. I can confirm that new date edits appear to stick now. Also, for folks who were concerned about previously edited dates migrating one day earlier (@Tion1), my spot checking shows corrected dates. So both issues are fixed, at least for me.
1 Like
Great news! Thanks so much for the confirmation.
Great, version 1.26.1.5762 fixed the problem, but not completely. The release year that shows when you select movies now shows the year 1900 if the release date is in the past.
