Your new update destroyed many libraries like mine. We customers were forced to have new features thrust upon us without even being asked. But my biggest issues have to do with the hijacking of my libraries for a new schema that apparently wasn’t tested correctly. This is a prime example of playing with peoples money and not caring.
I want a refund.
How did it ruin your library? Can you be specific?
For your Plex Pass, you can contact the billing department. You can find the link at the bottom of this page.
All you have to do is read the forums. I am so ■■■■■■■ angry that the new schema prevents my abilities to downgrade with an intact library. We users have had to sacrifice usability for features that you employees wanted, whilst being condescending. There is no fix for us power users or customers to even implement ourselves. And the “fixes” suggested DON’T WORK IN YOUR NEW ENVIRONMENT. So…yes. your product sucks now. In one update, across the internet, people like me are pissed.
Next question.
Rule #1 - “Once you have their money you never give it back”
Ferengi and Plex, who can tell the difference?
The Nagus is real here:joy:
Start here:
https://www.plex.tv/contact/?option=plex-pass-billing
However, you’d likely achieve a better result by outlining your specific issue(s) here and letting folks try to assist.
The way you quote these rules I’m starting to believe you are Ferengi.
The new schema Plex uses to rewrite the database on release 1.26 is corrupt. It makes the database only work with that new release. The timestamps and columns will not match or open in any prior release. I’ve been doing this for some years. The schema cannot be rewritten in Sqlite and it cannot be reversed. So. Yea. That sucks. Being stuck on a beta trash version sucks. Having no control to revert is a problem and I’m not the only one dealing.
Plex Media Server, by default, backs up your database every three days, and keeps the four most recent backups. Mine currently go back to 4/7, for example. So, you do have options for recovery, assuming you caught whatever error is causing this consternation soon enough.
Having said that, I just successfully downgraded my Windows test server from 1.26.0.5715 to 1.25.9.5721 with no issues. So you may need want to expand on your problem description with some specifics. Assuming you want assistance.
That isn’t always the best option. Rewriting the database is the issue. Having a backup doesn’t help me.
Expand what? The Schema environment is broken and i can’t revert back. That is a huge problem. Don’t be a dick.
Expand on what, specifically, broke for you. As I’ve indicated, I was able to roll back from the current beta release to stable. What I’m suggesting is that this problem may be specific to your environment. Additional details might help in determining how to help you recover.
I wouldn’t dream of it. And there’s really no reason to get salty; I can assure you, I don’t type on these forums just to see my words in print. If I’m doing so, it’s because I think I can help.
The Sqlite cannot change the library.db environment to revert back to the old structure by us users. The timestamps in unix are all screwed up. The database is corrupt and will only work on one version of a beta. I think that’s enough to be upset about.
In nothing you’ve typed to this point have you stated clearly what you’re attempting to do and what specifically is failing. You’ve provided only generalizations.
How, specifically, are you attempting to revert to the old structure? Plex will do this automatically for you if you downgrade versions; part of the first-run process is it checking the database version and running any migration necessary to normalize it.
Since you mentioned sqlite, I assume that you’re attempting to make manual modifications to the database, based on your previous understanding of the schema. Is that correct? If so, are you upset that they modified their proprietary schema?
Anecdote: Some time back I was interested in learning how Plex stored their Live TV & DVR EPG data. I was curious if I could reverse engineer the DB schema and write a utility which read the currently-stored data and dump it to an XMLTV-compliant XML file. I could, and did. However, I understand that that schema can change at any time; and I won’t be angry if it does.
That is not happening under the new schema. My databases are not being rewritten under and previous release.
Are you saying that you downgraded from 1.26 to 1.25, but the datetime column contents weren’t migrated correctly?
There were many errors when i looked at the db. A lot of them have to do with time and the program replacing date added or date modified tags during the update to 1.26. When I downgraded or did the SQLITE repair, i get constraint errors and mismatching data. But the corrupt database and my backups only work on 1.26.
Do you also manually make changes to the database?
I ask because I’m wondering if there’s a mixture of YYYY-MM-DD HH:MM:SS and epoch-style seconds in the DB now.
No. They only thing I do is read it to make sure things are in order. It’s been solid since Plex was on XMBC.
I tried to change things after i realized the problem. By then I realized that Plex made it impossible to revert or write on the database in 1.26. There isn’t a consumer level tool to fix this.
I just upgraded a server to 1.26 and then downgraded back to 1.25.
The downgrade appears to have correctly migrated everything. No errors I can immediately see. In fairness it’s a test server with a small database.
You might share logs or more specific details if you’re looking to resolve the issue.
