Bug 38082: Advanced editor does not save the selected framework

When creating a fresh record in the advanced editor, it does not
save the framework selected from the Settings dropdown.

Test plan:
==========

1. Enable the advanced editor feature (EnableAdvancedCatalogingEditor).
2. Start editing a new record in the advanced editor.  Fill in the
   mandatory fields, select a framework (other than Default) from the
   Settings dropdown, save the record.
3. Select view -- note that the record has been saved with the Default
   framework.
4. Apply the patch; restart_all; refresh the browser window.
5. Repeat p. 2.
6. Select view -- you should now see that the record has been saved with
   the correct, selected framework.

Signed-off-by: Roman Dolny <roman.dolny@jezuici.pl>
Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov>
Signed-off-by: Katrin Fischer <katrin.fischer@bsz-bw.de>
(cherry picked from commit 145bc398c1)
Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
This commit is contained in:
Janusz Kaczmarek 2024-10-03 18:22:39 +00:00 committed by Lucas Gass
parent 6bde7f52b9
commit f1c9a95c3a
1 changed files with 1 additions and 1 deletions

View File

@ -12,7 +12,7 @@ export class CataloguingAPIClient extends HttpClient {
return {
create: bib_info =>
this.post({
endpoint: "new_bib/frameworkcode=%s".format(
endpoint: "new_bib/?frameworkcode=%s".format(
bib_info.frameworkcode
),
body: bib_info.record.toXML(),