Angular Holdings Editor - sort out where holdings templates are saved
Bug #1975742 reported by
Galen Charlton
This bug report is a duplicate of:
Bug #1957179: Holding template creation fails in holdings editor in 3.8.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
The Angular Holdings editor retrieves templates from a server-side setting (cat.copy.
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+
| tags: | added: angular angularjs cat-templates |
| Changed in evergreen: | |
| status: | New → Confirmed |
Revision history for this message
| Galen Charlton (gmc) wrote | #1 |
| description: | updated |
| tags: | added: regression |
| summary: |
- Angular Holdings Editor - sort out where holdings tempalates are saved + Angular Holdings Editor - sort out where holdings templates are saved |
To post a comment you must log in.
(Noting that when I filed the bug, I had thought that the Angular and AngularJS holdings templates didn't have the same format. They do, however, so we should be able to preserve compatibility once the Angular editor starts saving its templates to the server.)