CAConfig Editor: Local Storage Caching prevents displaying new parameters correctly

Description

steps to reproduce:

  1. install our sample application https://github.com/wcm-io/wcm-io-caconfig/tree/develop/sample-app

  2. open a configuration http://localhost:4502/content/contextaware-config-sample/en/config.html#/io.wcm.caconfig.sample.config.ConfigSample

  3. keep the browser open

  4. add a new configuration option to https://github.com/wcm-io/wcm-io-caconfig/blob/develop/sample-app/bundles/core/src/main/java/io/wcm/caconfig/sample/config/ConfigSample.java

  5. deploy the sample application again

  6. refresh the browser window

  7. the new parameter is displayed, but without an entry field, see

workaround - the new parameter is displayed correctly if either:

  • the browser is closed completely and opened again

  • browser cache (including local storage) is cleared

Attachments

1

Activity

Show:

Stefan Seifert June 28, 2020 at 7:52 AM

thanks!

David Ding June 27, 2020 at 12:40 PM

- Fix pushed to project's develop branch.

Stefan Seifert April 28, 2020 at 3:54 PM

yes, i can still reproduce the problem as described, tested on windows with current chrome and firefox
i've not disabled any of the default caching behavior in the browsers

David Ding April 8, 2020 at 10:59 AM

- could you check if this is still reproducible?

I understand why the bug should occur, but when I follow your steps to reproduce, it is working correctly for me (have tried Chrome and Firefox)

Jurgen Brouwer February 21, 2020 at 9:05 AM

+1

Ran into the same issue a couple of times already. The workaround for clearing the local storage works, but it’s easy to miss/forget this step.

This happens often in projects where we have multiple branches that add/remove properties in a config. After a new deployment this would cause the unwanted behaviour.

Fixed

Details

Assignee

Reporter

Components

Priority

Created July 18, 2019 at 1:33 PM
Updated June 28, 2020 at 7:52 AM
Resolved June 27, 2020 at 12:40 PM