Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't save settings #2571

Open
joelstitch opened this issue Mar 17, 2016 · 6 comments
Open

Can't save settings #2571

joelstitch opened this issue Mar 17, 2016 · 6 comments

Comments

@joelstitch
Copy link

Whenever I try to save my settings I get a message saying "There was an error". There's no trace of the error on the logs. It says that its up to date. I also tried doing a fresh install and still the same. All the folders have the right permissions. Everything works fine I just cant save any new changes to the settings.

I am using Ubuntu Server 14.04

@TutenStain
Copy link

Same. However the settings actually get saved.

@joelstitch
Copy link
Author

I just noticed that today. I guess it doesn't matter as long as the
settings get saves. But I would like to know what's the error.
On Mar 19, 2016 5:13 PM, "Barnabas Sapan" [email protected] wrote:

Same. However the settings actually get saved.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#2571 (comment)

@joelstitch
Copy link
Author

Actually I thought it was saving the settings but if you refresh the page the settings go back to how they were so it doesn't save them.

@sfunk1x
Copy link

sfunk1x commented Jul 25, 2016

This is still happening in Master.

2016-07-24 19:52:05 INFO Writing configuration to file
2016-07-24 19:51:07 INFO Headphones is up to date
2016-07-24 19:51:07 INFO Retrieving latest version information from GitHub

The settings are saved as one would expect, but there is still a popup alerting the user that an error has occurred. This happens on checking for a new update as well. As far as I can tell, the settings are saved each time so functionally it's mostly there, but the messaging is erroneous.

@maxkoryukov
Copy link
Contributor

Just information:

If you will try to search for the source of the error, you will find, that JS on the client side for notifications has a lot of spaghetti-code and is used not only on the Settings page..

I've tried to rewrite it (in #2590), but there is a lot of dependencies, and one fix for the "Settings" page could break down notifications on other pages... I think, someone do that.. 😞

@draftzero
Copy link

I'm having a similar issue, I'm unable to update Plex Token. I can save it, but if I refresh, it loses it's settings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants