When a value, e.g., the event name, is changed via the site configuration form (https://pace3.lauf-gegen-rechts.de/admin/changeTheme), the value gets updated but the result of the corresponding GET request, that provides the currently configured settings, will be cached and therefore, if the admin opens the site configuration form again, the old values will be set in the form.
As a goal of this story, we want to ensure that only the current values are displayed.
This could happen by invalidating the cache of the GET request or to never use cache for this request at all.
When a value, e.g., the event name, is changed via the site configuration form (https://pace3.lauf-gegen-rechts.de/admin/changeTheme), the value gets updated but the result of the corresponding GET request, that provides the currently configured settings, will be cached and therefore, if the admin opens the site configuration form again, the old values will be set in the form.
As a goal of this story, we want to ensure that only the current values are displayed. This could happen by invalidating the cache of the GET request or to never use cache for this request at all.