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

bug: alerts[0].localpath blanked after Save Changes #8

Closed
ab7pa opened this issue Sep 8, 2020 · 1 comment
Closed

bug: alerts[0].localpath blanked after Save Changes #8

ab7pa opened this issue Sep 8, 2020 · 1 comment

Comments

@ab7pa
Copy link
Contributor

ab7pa commented Sep 8, 2020

Go to Advanced Configuration and enter a URL in alerts.localpath then click Save Setting. The setting becomes active and Local Messages are displayed correctly after an AAM Refresh. Reboot the node and the alerts.localpath correctly persists across a reboot. However, go to Basic Setup and click Save Changes then return to Advanced Configuration to see the alerts.localpath value has been removed. The alerts.localpath value should persistent across a normal Save Changes.

@ae6xe ae6xe transferred this issue from aredn/aredn_ar71xx Dec 16, 2020
@ab7pa ab7pa changed the title alerts[0].localpath blanked after Save Changes but: alerts[0].localpath blanked after Save Changes Jan 5, 2021
@ab7pa ab7pa changed the title but: alerts[0].localpath blanked after Save Changes bug: alerts[0].localpath blanked after Save Changes Jan 5, 2021
@ab7pa
Copy link
Contributor Author

ab7pa commented Apr 24, 2021

I am no longer seeing this issue.

@ab7pa ab7pa closed this as completed Apr 24, 2021
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

1 participant