Bug 34177 - Call number browser is not opening in new window
Summary: Call number browser is not opening in new window
Status: RESOLVED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-30 19:17 UTC by Laura Escamilla
Modified: 2023-09-08 15:56 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Laura Escamilla 2023-06-30 19:17:20 UTC
The call number browser is not opening in a new pop-up window as expected. This causes an issue in workflow whenever a library uses it because submitting a search will cause the Koha navbar and header_search to disappear. 

/cgi-bin/koha/cataloguing/plugin_launcher.pl
Comment 1 Owen Leonard 2023-07-03 11:05:03 UTC
This works for me in my test system. Is there a JavaScript error in the browser console?
Comment 2 Laura Escamilla 2023-07-03 14:52:29 UTC
(In reply to Owen Leonard from comment #1)
> This works for me in my test system. Is there a JavaScript error in the
> browser console?

Uncaught ReferenceError: authorised is not defined
    <anonymous> http://localhost:8081/cgi-bin/koha/cataloguing/plugin_launcher.pl?q=&plugin_name=cn_browser.pl&popup=&cn_source=ddc:517
    jQuery 13
        e
        t
        setTimeout handler*Deferred/then/l/<
        c
        fireWith
        fire
        c
        fireWith
        ready
        B
        EventListener.handleEvent*
        <anonymous>
        <anonymous>
Comment 3 Katrin Fischer 2023-07-16 13:33:14 UTC
I also tested and it worked correctly.

* Updated framework BKS to link 952$o to cn_browser
* Searched for a record, add item
* Opened the plugin

Does this match what you did? What could be the difference?

Could any local JS have gotten in the way?

As it complains about 'authorised' - any editing limitations in place?