Bug 7624 - Constrain new category code field to 2 Characters in categorie.pl
Summary: Constrain new category code field to 2 Characters in categorie.pl
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 3.6
Hardware: PC Windows
: P5 - low enhancement
Assignee: Kyle M Hall
QA Contact: Ian Walls
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-29 16:09 UTC by Larry Zuares
Modified: 2012-10-26 00:51 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:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Larry Zuares 2012-02-29 16:09:39 UTC
Please constrain the "category code" dialog box to 2 characters or allow for longer category code length. As it currently stands, users can add category codes in excess of 2 characters, which causes 500 errors when quick-searching patrons, in member.pl.
Comment 1 Liz Rea 2012-02-29 19:00:08 UTC
I'm going to need a screen cap or longer description to better understand what the issue here is. 

Would you provide one?
Comment 2 Katrin Fischer 2012-02-29 19:03:49 UTC
Hi, 
which version are you looking at? You should be able to use categorycodes up to 10 characters everywhere in Koha without having any problems. If there is a place where it does not work - it's a bug there and should be fixed. Can you give a step by step description of what you are doing and what the failing code was?
Comment 3 Larry Zuares 2012-03-22 11:42:20 UTC
I had created patron category codes for each grade level at a school, ie. GRADE01, GRADE02, etc. I imported the students and tried to browse by last name, using members.pl. I received 500-code errors, in the browser, on each page. Since I didn't have the problem when I was using a 2-digit category code, namely "ST" for student, I changed all of the category codes to 2-digit codes, ie. 01, 02, etc., which resolved the problem. I'm currently on version 3.6.2.3. I apologize, but I don't really have a test environment, right now, to replicate the problem. If anyone else can replicate this problem they can reopen this bug; however, at this point I will mark this bug as resolved.

-Thanks