Added content cache can't be cleared in angular
Bug #1939162 reported by
Elaine Hardy
This bug affects 22 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.11 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
With the change to the static patron view, and the solution to that - https:/
Correcting the added content often requires clearing the cache. Prior to angular, there was a button in the OPAC view in the staff client that cleared the cache. Since that embedded OPAC view is no longer in the staff client, there is no way within angular to clear the cache
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: staffcatalog |
tags: | added: regression |
tags: | added: usability |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Discussed in Cat IG. Confirming this functionality is not available in angular staff catalog (testing in 3.7) and is missed for the purpose of seeing the effect of changes made in a timely manner. Use case: refreshing cover images. Logging out and back in does not consistently clear cache to confirm changes; neither does a hard refresh of the screen.
Workaround now is to make changes and go to public catalog to see if changes take effect.
The refresh of content in the staff client is often not fully reflected for 24 hours or more without the ability to clear added content cache at the time changes are made.