Cannot edit an authority record twice without reloading authorities,

Bug #1233350 reported by Steve Callender
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Fix Released
Undecided
Unassigned
2.5
Fix Released
Undecided
Unassigned
2.6
Fix Released
Undecided
Unassigned

Bug Description

This was tested in 2.4.0.

When you go to Manage Authorities, do a search, and edit an authority, everything appears to work fine. When you do a second search from still within the same manage authorities screen, it will no longer allow you to edit any more authorities. You have to completely reload "manage authorities" to continue editing.

You should be able to search and edit for as many authorities as you need from within this screen and not have to reload after every edit.

Steve

Tags: authority
Revision history for this message
Steve Callender (stevecallender) wrote :

Tested on 2.4.1 as well.

Yamil (ysuarez)
tags: added: authority
Revision history for this message
Srey Seng (sreyseng) wrote :

Can confirm behavior on 2.4.1 here as well.

Revision history for this message
Yamil (ysuarez) wrote :

Here are the steps to recreate this bug. I am looking into fixing this issue, but I probably need help from more experienced developers.

1) in "Manage Authorities" perform a search,

2) open the authority record by using "actions" drop-down menu, select "edit"

3) edit, save and close auth record

4) then perform another authority search

5) go to the "actions" drop-down menu to "edit" any authority in the new search result

6) the drop-down activates, "edit" can be selected, but the authority record pop-up record never materializes.

7) If you then try to activate the drop-down menu again, the button does not respond at all. Essentially the Manage Authorities page is deemed inoperable.

8) The only way to proceed is to hit the reload button and begin an authorities search all over again.

Revision history for this message
Erica Rohlfs (erohlfs) wrote :

How timely, Yamil. I was just trying to edit authorities this morning and saw the same behavior. I was running version 2.6.3.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Dan Wells (dbw2) wrote :

This bug should be fixed by the code posted in bug #1379824.

Changed in evergreen:
milestone: none → 2.7.1
no longer affects: evergreen/2.5
Revision history for this message
Yamil (ysuarez) wrote :

I tested the commit that Dan created for his related bug ( https://bugs.launchpad.net/bugs/1379824 ) in EG 2.7.0 and 2.6.2 using the concerto dataset.

Here is my signoff branch...

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/ysuarez/lp1379824_fix_pcrud_disconnects_signoff

Thanks for looking into it Dan (and Remington).

Though, others might have another approach to fix this issue.

Revision history for this message
Ben Shum (bshum) wrote :

Fix pushed from other bug, marking these as fix committed too.

Changed in evergreen:
status: Confirmed → Fix Committed
Changed in evergreen:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.