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

[Bug 7619] New: 3M self checkout don't work in France
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '13

20 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7619 Bug #: 7619 Summary: 3M self checkout don't work in France Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: ASSIGNED Severity: blocker Priority: P2 Component: SIP2 AssignedTo: paul.poulain(a)biblibre.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha.sekjal(a)gmail.com CC: frederic(a)tamil.fr, gmcharlt(a)gmail.com The 3M self checkout used to work perfectly for Koha 3.2 in France. Since Koha 3.6, they don't work anymore. I've asked some english natives, they don't have any problem with this feature, it seems it's french specific ? However, the patch to fix this problem is tiny, even if it was very hard to spot what/where was the problem. Frederic = you're encouraged to test & signoff this patch and confirm it fixes the problem. Galen = if i'm not wrong, you should be interested to test this patch, also for Evergreen. ALL ENGLISH ppl = you *MUST* also test that this patch don't *break* anything I don't understand why replacing a \r by a CRLF fixes the problem, and it may cause some problems to non-french self checkouts ! (I won't push this patch until i've strong feedback it don't break anything for others) -- 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 30

[Bug 5586] New: SIP line-endings should use proper SPEC-compliant \r
by bugzilla-daemon＠bugs.koha-community.org 20 Apr '13

20 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5586 Summary: SIP line-endings should use proper SPEC-compliant \r Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: SIP2 AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Line-endings have been a longstanding problem because of variations in implementations. But we should still tryto default to the correct thing, according to what standards are available. -- 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 14

[Bug 3059] generate password with forgot password link
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '13

19 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3059 Eric Bégin <eric.begin(a)inLibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |eric.begin(a)inLibro.com Resolution|--- |DUPLICATE --- Comment #2 from Eric Bégin <eric.begin(a)inLibro.com> --- *** This bug has been marked as a duplicate of bug 8753 *** -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 10082] New: don't delete borrower attributes
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '13

19 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10082 Bug ID: 10082 Summary: don't delete borrower attributes Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you delete a borrower their record goes into the deleted_borrowers table, but their attributes are completely lost. If you to do stats on these fields or recover deleted borrowers via the db you don't have that info anymore. It should either have it's own deleted_ table or be kept in the current table. Nicole -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 7401] New: Shelving Location facet instead of Branch facet when only 1 branch configured
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '13

19 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7401 Bug #: 7401 Summary: Shelving Location facet instead of Branch facet when only 1 branch configured Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: ian.walls(a)bywatersolutions.com If there is only one branch configured in Koha, it doesn't make any sense to put a limiter on branchcode in search results. Having a limiter on shelving locations within that branch, though, would be very handy. -- 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 60

[Bug 2720] Overdues which debar automatically should undebar automatically when returned
by bugzilla-daemon＠bugs.koha-community.org 19 Apr '13

19 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 mathieu saby <mathieu.saby(a)univ-rennes2.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mathieu.saby(a)univ-rennes2.f | |r -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10077] New: pass extended patron attirbutes via Borrower SIP protocals
by bugzilla-daemon＠bugs.koha-community.org 18 Apr '13

18 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10077 Bug ID: 10077 Summary: pass extended patron attirbutes via Borrower SIP protocals Classification: Unclassified Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: melia(a)bywatersolutions.com CC: colin.campbell(a)ptfs-europe.com This is an enhancement idea (not sponsored, just putting the idea out there). Some libraries think it would be nice if you could pass extended patron attributes via SIP. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 9885] New: Passwords generated by command line scripts are weak
by bugzilla-daemon＠bugs.koha-community.org 18 Apr '13

18 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9885 Bug ID: 9885 Summary: Passwords generated by command line scripts are weak Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: peterAtKohaBugzilla(a)pck.co.nz The command line scripts koha-reset-passwd and koha-create in debian/scripts generate fairly weak passwords. Staff passwords are generated as an eight-character "readable" pwgen password, as is the mysql password. The Zebra password is generated as a 12 character readable password. The eight character passwords are fairly vulnerable - see the discussion at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276976 or the somewhat more dry discussion at http://ix.cs.uoregon.edu/~butler/pubs/password.pdf Do these passwords really need to be THAT friendly? I would suggest: - changing the zebra password and mysql passwords to 16 character "secure" passwords, ie generated with pwgen -s 16 1 - changing the patron password to a 12 character not-secure password. I'm happy to write the patch for these two files if there is consensus that it should be actioned. I have checked gitk and while I read the current debian koha-common version of the scripts (package 3.11-1~git+20130321124944.90dfa923), this does not appear to have changed in the master version. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 2720] Overdues which debar automatically should undebar automatically when returned
by bugzilla-daemon＠bugs.koha-community.org 18 Apr '13

18 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2720 Melia Meggs <melia(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff --- Comment #17 from Melia Meggs <melia(a)bywatersolutions.com> --- I'm just changing status back to "Needs Signoff" for the new patch that Kyle attached on 3/21. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 9997] New: Suspected typo in patron self registration code
by bugzilla-daemon＠bugs.koha-community.org 18 Apr '13

18 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9997 Bug ID: 9997 Summary: Suspected typo in patron self registration code Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While translating this: %s %s [%% SET field_display_names = { surname => "Surname" firstname => "First name" title => "Title" othernames => "Other names" initials => "Initials" streetnumber => "Street number" streettype => "Street type" address => "Address" address2 => "Address 2" city => "City" state => "State" zipcode => "Zip code" country => "Country" email => "Email" phone => "Primary Phone" mobile => "Primary Mobile Phone" fax => "Fax" emailpro => "Secondary email" phonepro => "Secondary phone" B_streetnumber => "Alternate address - street number" B_streettype => "Alternate address - street type" B_address => "Alternate address" B_address2 => "Alternate address 2" B_city => "Alternate address - city" B_state => "Alternate address - state" B_zipcode => "Alternate address - zip code" B_email => "Alternate address - email" B_phone => "Alertnate address - phone" dateofbirth => "Date of birth" contactname => "Contact - last name" contactfirstname=> "Contact - first name" contacttitle => "Contact - title" relationship => "Contact - relationship" ethnicity => "Ethnicity" ethnotes => "Ethnicity notes" sex => "Sex" altcontactfirstname => "Alternate contact - first name" altcontactsurname => "Alternate contact - surname" altcontactaddress1 => "Alternate contact - address" altcontactaddress2 => "Alternate contact - address 2" altcontactaddress3 => "Alternate contact - city" altcontactstate => "Alternate contact - state" altcontactzipcode => "Alternate contact - zip code" altcontactcounty => "Alternate contact - county" altcontactphone => "Alternate contact - phone" smsalertnumber => "SMS alert number" } %%] I was wondering if altcontactcounty => "Alternate contact - county" shouldn't be country to match the field in the database? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9