I find that PLEX is very specific about the types of files you put in your libraries. So if you try to create a library of home videos, and choose ‘other videos’ it seems to say ‘can not save changes’ Whereas if you go into advanced and change it to ‘The Movie Database’ suddenly it works. I was able to save all my changes after fiddling with the library advanced settings drop down about which agent it’s using. The side effect though is that they may not play if you choose the wrong type of agent for the type of file. Plex seems very closed regarding file types in this way.
If you don’t put information in that is in the correct format (such as the date of the TV or movie) then it will not save it. I went through the information that I could change step by step (changing one thing, saving it, then back again) and isolated my problem by doing this. This might help someone else.
1 Like
This appears to be an ongoing issue for many years. I also have the same issue, when I go to fix, or edit movies in my library. Plex matched Arrival with The Arrival - I split them apart and then went to edit the year, and movie and will not save the changes. However, I can select fix match to make the change.
Issue occurs with Edge, Chrome & IE. I tried the //127.0.0.1 & //DNShostname & //10.0.0.XXX
All Plex urls have been added to trusted sites
Plex Version 3.67.1
WIndows 10 Build 17134
If the syntax of what is being entered is not as expected, you would get the error Your changes could not be saved
Suggest you get screenshot and server logs and for this type error would need verbose and debug logging in server settings (settings / server / general / show advanced)
Reproduce the problem, get a screenshot and details of exactly what was entered and where and download the server logs and attach the zip and screenhots and include the requested information
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Thank you for this tip! I couldn’t save changes because I was only entering year of the movie (no month or day). Entering the full date did the work for me.
1 Like
Thank you so much for posting this!!! I’ve lost years of my life over this issue. I tried 4 browsers on Linux and Windows, removed all my extensions from all my browsers and nearly ditched plex for good. Thank you!
Count me in for having lost 2 days over this.
This issue has been confounded because for many months I have been able to simply enter a four-digit “Year” when using Plex server (latest version) running on my NAS – and can still do so to this very day. There, the server simply defaults to YYYY-01-01 before saving. I was foolish enough to think that there was something wrong with my new MacOS/Safari when installing a server instance there and repeating this same task (over and over and over…).
A message to those writing the code: Of course you know “what” has thrown the error in order to post the message “Your changes could not be saved”. Why not post the specific error to the user, such as “Incorrect date format - nothing saved”. That simple change would save much time for users and much time posting and replying in these forums. I suspect that there are few users who care about the month and day. But often, Plex gets the year wrong and we simply want to update it (without needing to look up the actual month and day). For my NAS server, when I simply enter the year (unlocked), then I can rescan and Plex will find the correct movie and enter the full date.
Guys -
I’m having the same issue on a new PMS build I stood up for testing on a new Ubuntu 18/04 x64 install. Whenever I attempt create or edit any library and click Save, it times out showing the error “Your changes could not be saved.”
If creating a new library, refreshing the page or clicking cancel will show the newly created library on the left bar, it it has default options selected - regardless of what you configured it as when creating it. If editing it, nothing changes yet it seems to start an immediate scan of the library you attempted to edit.
So far I’ve tried the below with the same erroneous results from all of them:
Accessed via 127.0.0.1 in local browser (Firefox)
Attempted via static IP of 192.168.0.235 and hostname of KNPlex for the following:
- Firefox (local system)
- Chromium (local system)
- Chrome on Windows 10 x64 (1809) PC (LAN PC)
- Internet Explorer on Windows 10 x64 (1809) PC (LAN PC)
- Edge on Windows 10 x64 (1809) PC (LAN PC)
LAN PCs are on same subnet and site added as trusted in IE
As I had previously changed my remote port to 31400 since it’s a test Plex server, I thought this may be the issue so changed it back to 32400 by unchecking option to manually specify port, then disabled remote access and tested again, but it wasn’t any help.
The only errors I’m seeing when monitoring the console in a separate window and attempting the edits are about x5 of the SLOW QUERY one below and x3 of the PubSub:
- SLOW QUERY: It took 340.000000 ms to retrieve 50 items.
- PubSub: Received notifyConnectivity event with incorrect async identifier (2f51a6f9-9068-4d2a-9b54-19b8744f5bde, expected cbb1c5e7-9603-4e03-bb61-728340fe5ad6)
I don’t remember this being an issue yesterday when I added the first couple of libraries after installation and don’t think I had it as the settings in those libraries are what I want them to be.
Any suggestions? Thanks
UPDATE
It seems that after I re-enabled IPv6, saved, then restarted Plex’s service; it made a small difference. Once I did this and tried to edit a libraries’s settings, it still timed out; yet half of the time it actually saves the change made after refreshing the page.
Sometimes, if I click “Save changes” again after it times out, it works correctly as it closes the window and saves the changes. I still get the “PubSub” error regardless, though. Finally, it seems the less number of changes I try to make, the better chance it has on working. I may only have to click Save changes 2-3 times if unchecking one options, but many if unchecking 3-4.
Thanks
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
