June 2021 - Koha-bugs - lists.koha-community.org

[Bug 27488] New: Rename system preference suggestion to OPACPurchaseSuggestions
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '22

28 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27488 Bug ID: 27488 Summary: Rename system preference suggestion to OPACPurchaseSuggestions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org find all of the places in the code that refer to the 'suggestion' system preference and rename them to 'OPACPurchaseSuggestions' write an atomic update to rename the suggestion system preference to OPACPurchaseSuggestions in the preferences table in the database rename the suggestion syspref in sysprefs.sql refer to bug 10328 for an example -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 18950] New: Elasticsearch - Add password access for admin functions
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '22

28 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18950 Bug ID: 18950 Summary: Elasticsearch - Add password access for admin functions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This patchset adds a parameter to the koha-conf.xml file: <elasticsearch_admin_password> When defined additional actions will be enabled on the Search engine configuration page Password must be entered and action chosen, if password matches the action will be performed -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20464] New: On public reports, the behavior of cache-expiry 0 is confusing to users
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '22

28 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20464 Bug ID: 20464 Summary: On public reports, the behavior of cache-expiry 0 is confusing to users Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a report is made public, 'cache-expiry' is the number of seconds that the results will remain cached from the last run -- *except* if this is set to 0, in which case the cache never expires. This behavior is *very* confusing to users, who expect the cache to expire immediately if the expiry is 0, and get exactly the opposite behavior. This is a frequent support issue -- This should at least be better labeled (perhaps with a javascript warning?), if we can't find a path toward changing the behavior. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 25100] New: Add ability to add custom text to top of the Self registration Form
by bugzilla-daemon＠bugs.koha-community.org 28 Jan '22

28 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25100 Bug ID: 25100 Summary: Add ability to add custom text to top of the Self registration Form Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It would be great if we could have a custom HTML setting for information at the top of the self registration field to make it easy for staff to add/edit information about how to follow up with their new card. We currently use jquery to add it, but it would be nice if it was a separate setting. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 28332] New: Requesting Mana token with accented name fails
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '22

27 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28332 Bug ID: 28332 Summary: Requesting Mana token with accented name fails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com CC: alex.arnaud(a)biblibre.com Test plan: - Go to Administration Share content with Mana KB (cgi-bin/koha/admin/share_content.pl) - in "Configure Mana KB" part, set your email and a name with accent (Université Foo), - click on "Send to Mana KB" => Fail. No mana token. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 23590] New: Allow to modify the manager of a suggestion
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '22

27 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23590 Bug ID: 23590 Summary: Allow to modify the manager of a suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org When a staff member modifies a suggestion, it is automatically attributed to the logged librarian. It would be very useful to have the option to select another user that will be the one in charge of this suggestion. This other user could also be notified by an email after the suggestion is modified. This feature probably means to create new fields in the ‘suggestions’ table to separate ‘managedby’ / ‘manageddate’ from the ‘lastmodificationby’ / ‘‘lastmodificationdate’ informations, but I think it will ensure a better follow up on the suggestions workflow. The BULAC (http://www.bulac.fr/) would like to sponsor this development. As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 166

[Bug 27312] New: Add a syspref to redirect patron after self registration
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '22

25 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27312 Bug ID: 27312 Summary: Add a syspref to redirect patron after self registration Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org We need to implement a workflow that looks like this: 1. A new patron self registers in the OPAC, with a temporary category code, including providing a social security number 2. After the data is saved, the patron is redirected to a Script (similar to opac/svc/auth/googleopenidconnect, but provided by a plugin) 3. The script redirects the patron again, to an OpenID provider, where (s)he has to login in a secure manner 4. After logging in, the user is redirected back to the Script, and the Script can tell what the correct social security number of the patron is 5. If the social security number provided by the OpenID provider matches one of a temporary patron, that patron is updated to a permanent patron We need to be able to set the URL that the user should be redirected to in step 2 above. This could be done in a couple of ways: 1. As a syspref This would be fairly simple. The syspref holds the URL and if it is set, the user is redirected at the right place in opac/opac-memberentry.pl 2. As a plugin hook The first plugin hook of the right type called would provide the URL and, if there is a URL, the patron is redirected. One advantage of the plugin hook approach is that the information about where to redirect the user would be contained in the same plugin that provides the Script. But a plugin hook does seem like a bit of overkill for providing a single, static URL. And I guess the plugin could set the syspref, if it wanted to, so I will submit a patch that uses a syspref. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 23944] New: Phase out use of jquery.cookie.js in favor of js.cookie.js
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '22

24 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23944 Bug ID: 23944 Summary: Phase out use of jquery.cookie.js in favor of js.cookie.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org The jQuery plugin we use for setting cookies is obsolete: https://github.com/carhartl/jquery-cookie -- "No longer maintained, superseded by JS Cookie: https://github.com/js-cookie/js-cookie" -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 19290] New: Add the ability to filter a result list on staff client
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '22

24 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19290 Bug ID: 19290 Summary: Add the ability to filter a result list on staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org It would be useful for the BULAC staff and patrons (http://www.bulac.fr/) to browse through selected records on a result list without saving them in a list. On the different results pages, we could select several records and use the “Return to results” / Previous” / “Next” links on one of theses records would go from one to the other of the select records and not the full result list. As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 22053] New: Ability to disable some plugins
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '22

24 Jan '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22053 Bug ID: 22053 Summary: Ability to disable some plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Today we can only disable all or none plugin by dealing with koha configuration. It would be interesting to be able to temporarily, or not, disable one or more without having to remove them from plugins directory. This could be useful for plugins called by hook like "intranet_catalog_biblio_enhancements_toolbar_button" or checkpw (see bug 20340). Disabling is not like uninstalling. Because here we want to keep the data and db structure created by the plugin in the case it would be enabled again. Also, uninstalled plugin are retrieved by GetPlugins method like installed ones. Work in progress... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 64