December 2013 - Koha-bugs - lists.koha-community.org

[Bug 5347] New: late order management
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5347 Summary: late order management Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Late_orders_acq_RF C OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 For lateorders, we will add fields for date and comment coming from the library. For claims, we will add * a claim counter, to know how many times an order has been claimed * a claim table, containing all the claims an order has, with the date of the claim and the content of the claim -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 99

[Bug 5576] New: Access Koha via SSL
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5576 Summary: Access Koha via SSL Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: P5 Component: System Administration AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 Some libraries want to access Koha over SSL. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 12

[Bug 10542] New: QueryParser + OpacSuppression doesn't allow search in 'all libraries'
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '14

29 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10542 Bug ID: 10542 Summary: QueryParser + OpacSuppression doesn't allow search in 'all libraries' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de CC: jcamins(a)cpbibliography.com When QueryParser is activated and OpacSuppression is used, you don't find any results for "All libraries" (pull down next to simple search in OPAC). -- You are receiving this mail because: You are watching all bug changes.

1 56

[Bug 10060] New: Self Checkout module does not honour circ control
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '14

28 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 Bug ID: 10060 Summary: Self Checkout module does not honour circ control Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz With Syspref settings of: CircControl - Use the checkout and fines rules of >> the library you are logged in at. HomeOrHoldingBranch - Use the checkout and fines rules of >> the library the item was checked out from. The web self check module isn't obeying these rules - it is using the library of the borrower doing the circulating, not the library assigned to the staff user required to log in to use the self check. To replicate: Ensure web self check is enabled Set CircControl to >> the library you are logged in at Set HomeOrHoldingBranch to >> the library the item was checked out from Create a staff user with "Circulate - remaining permissions," with homebranch as Library A (your choice which of your branches is library A) Set that user as the auto login user for self check Hit the self check interface at cgi-bin/koha/sco/sco-main.pl log in or use the card number for a borrower from Library B, circulate an item. View the item's circulation history, it will be from Library B instead of Library A -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8148] New: ldap authentication should FAIL if ldap contains NEW password, and user types the PREVIOUS password
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8148 Priority: P5 - low Change sponsored?: --- Bug ID: 8148 CC: dpavlin(a)rot13.org Assignee: gmcharlt(a)gmail.com Summary: ldap authentication should FAIL if ldap contains NEW password, and user types the PREVIOUS password Severity: enhancement Classification: Unclassified OS: All Reporter: heupink(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Authentication Product: Koha The way ldap authentication works now is that the patron password is both in ldap and in mysql, usually the primary location being ldap. If sys admins change the userpassword, it's changed directly in ldap, and koha still has the old password stored in mysql. If the user then tries to logon with the OLD password, he should get 'access denied'. But instead he/she gets in, using the old, no longer valid, password. Various possible solutions: The best one: - an option not to store the password in mysql AT ALL (passwords are very sensitive info, I would like to store them in as few places as possible) Two other solutions: - a 'flush authentication cache' button in the staff interface? - a syspref to select the order of precedence when authenticating a user? -- You are receiving this mail because: You are watching all bug changes.

1 54

[Bug 10434] New: More flexibility to handle VAT / Shipping & handling
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10434 Bug ID: 10434 Summary: More flexibility to handle VAT / Shipping & handling Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com More flexibility to handle VAT / Shipping & handling -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 10854] New: Choose a CSV profile for exporting serial claims
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10854 Bug ID: 10854 Summary: Choose a CSV profile for exporting serial claims Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Bug 10853 allows to create CSV profile with DB fields. This feature will allow to select a defined CSV profile for serial claims. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 10648] New: In records merge greatest field can not be added
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10648 Bug ID: 10648 Summary: In records merge greatest field can not be added Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When merging 2 records (/cgi-bin/koha/cataloguing/merge.pl), the destination record is build using the fields and subfields checked in source records. When a field is checked, the javascript code searches in destination record a field with a greater tag number to insert new field before. When the new field tag number is greater than all existing field tag numbers, the field is not added. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 7462] New: duplicate patron shows flags
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7462 Bug #: 7462 Summary: duplicate patron shows flags Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha.sekjal(a)gmail.com CC: gmcharlt(a)gmail.com When you duplicate a patron record the duplicate has the patron flags showing. The patron flags should only show when editing a patron not when adding a new patron. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 9

[Bug 7237] New: duplicating patron not using patron's branch
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '14

27 Aug '14

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7237 Bug #: 7237 Summary: duplicating patron not using patron's branch Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: ian.walls(a)bywatersolutions.com CC: gmcharlt(a)gmail.com When duplicating a patron the branch chosen is not the branch of the patron I was duplicating but the branch I'm logged in to the staff client at. I think it should be the branch of the previous patron since I am duplicating them. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 11