Settings and Preferences not saving.
Created 6 years ago by rcrowt

I am running a fresh install of the latest PyroCMS with no extra plugins/themes installed. When I change any system settings or preferences and click "update" the settings aren't saved. The form is posted to the server but the page is simply reloaded with the old settings. It doesn't matter what setting/preference I change (title, numeric value etc) it saves nothing.

There is no flash saying it saved successfully and there is nothing in the error log saying there was a problem. I have no issues updating other parts of the app such as user details, page content or navigation items.

Any ideas? Thanks

dah  —  6 years ago

I have the same problem on a fresh installation from today. In addition I also have a problem where I can't change the e-mail address of a user. Not sure if it's related to the issue (it actually pre-fills my own address).

ryanthompson  —  6 years ago

@dah I had issues with this and it was Google Chrome auto-populating and being aggressive - I've had to disable it in our admin. Checking into the other issue with settings..

piterden  —  6 years ago

Also, user profile page, has the same problem with auto-populating in chrome. If I opened any user profile, email and password had replaced by my own. Could we disable it programmatically, for some pages? It caused hard annoying.

piterden  —  6 years ago

@ryanthompson I had checked it in Firefox. The same situation. Settings are not remembering for a fresh Pyro install. There is not a browser problem!

Please, test it on a new fresh install.

rcrowt  —  6 years ago

Also tested in in Firefox and IE (all extensions disabled) and it still doesn't work.

rcrowt  —  6 years ago

I updated my install which included @piterden 's fix and now the problem is solved.

Thank you.

huglester  —  6 years ago

any progress on this? same issue

I posted issue earlier too: https://github.com/pyrocms/pyrocms/issues/4298 "anomaly/streams-platform": "1.2.237" - seems to be working.

huglester  —  6 years ago

solved in v1.2.251