-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Modifications to existing entries in default instance settings do not persist #1095
Comments
After entering the key and value, did you press + at the right? |
When modifying an existing entry, there is only the X button to delete it. |
That's because there is no ability to edit existing entries atm. Has been requested |
Oh, okay. Maybe the textboxes should be readonly in the meantime to prevent confusion |
This has been addressed in a subsequent update. |
The issue does not seem to be fixed, it is still present on AMP version 2.5.1.6 - 20240816.1. But maybe you mean that a fix has been made but not yet released? |
Bug Report
System Information
Operating System
Ubuntu Server 22.04.4
AMP Version and Build Date
2.5.0.8 - 20240502.1
AMP Release Stream
Mainline
I confirm:
Symptoms
What are you trying to do?
Edit an existing entry in
Configuration > New Instance Defaults > Default Settings
.What are you expecting to happen?
That the changes are saved.
What is actually happening?
The node and value gets reset after refreshing the page, even if you attempt to save your changes by pressing enter or clicking outside the textbox.
Reproduction
Configuration > New Instance Defaults > Default Settings
.Node
orValue
. For example try to change the value ofCore.Privacy.AllowAnalytics
tofalse
.Default Settings
again and observe that the changes were not saved.The text was updated successfully, but these errors were encountered: