| 2022-05-25 19:51:48 |
Galen Charlton |
description |
The Angular Holdings editor retrieves templates from a server-side setting (cat.copy.templates), but saves them to as a local storage item (key also cat.copy.templates).
As a consequence, users can see the templates that they created in the AngularJS holdings editor, but any changes they make would not appear to take effect. Somebody starting from a fresh database would appear to be able to save templates, but they wouldn't actually persist.
Noting that because the AngularJS holdings editor also uses the 'cat.copy.templates' key but a slightly different format, having the Angular holdings editor save templates to the same key might break the AngularJS holdings editor - which is a problem because various interfaces in Evergreen still point to the AngularJS version.
Evergreen 3.8+ |
The Angular Holdings editor retrieves templates from a server-side setting (cat.copy.templates), but saves them to as a local storage item (key also cat.copy.templates).
As a consequence, users can see the templates that they created in the AngularJS holdings editor, but any changes they make would not appear to take effect. Somebody starting from a fresh database would appear to be able to save templates, but they wouldn't actually persist.
Evergreen 3.8+ |
|
