geonetwork / geonetwork/core-geonetwork
Admin console Settings cached behaviour
- Dominant language
- Java
- Stars
- 521
- Forks
- 514
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 19
Description
**Describe the bug**
When going to the Administration Console settings and then changing some values it seems that the application caches the first version of the settings.
In fact, if you save the new settings, when you go back to the Admin console page you do not see them. It seems that the application hasn't saved them. This though is not true, since if the page is reloaded by clearing the browser's cache, the new settings appear.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to Admin Console -> Settings
2. Change whatever value you want
3. Save settings (the "Settings updated" message appears)
4. Go to another menù and then come back to the Admin -> Console settings
The settings in the page seem to be the old ones and not the new ones.
If you recharge the page by clearing the browser's cache, the new setting values appear.
This issue might be related to #4739 issue.
**Desktop (please complete the following information):**
- Browser: chrome & firefox tested
- GeoNetwork Version 3.10.2
- Docker version 19.03.8, build afacb8b docker-compose version 1.25.4, build 8d51620a
Contributor guide
Research direction
Reproduce the issue from Administration Console → Settings using Chrome or Firefox, then compare the displayed values after saving, visiting another menu, and returning. The fix is complete when saved settings appear without clearing the browser cache; check whether the behavior is related to issue #4739.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100