- Koha-devel - lists.koha-community.org

[Bug 163] New: In the field for the member's sex, only F shows up
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=163 Summary: In the field for the member's sex, only F shows up Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net In the new member and update member forms, there is only a label for F, none for M. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 167] New: buildrelease.pl doesn't know about the new directory structure
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=167 Summary: buildrelease.pl doesn't know about the new directory structure Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: minor Priority: P2 Component: Installation AssignedTo: tonnesen(a)cmsd.bc.ca ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net buildrelease does a cvs log buildrelease.pl, but buildrelease.pl is now in misc/, so it doesn't know about the 1.3.2 and 1.3.3 versions because it cannot see the tags. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 129] Choosing to install MARC tables gave errors
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=129 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 166] New: Member details form shows yyyy/mm/dd, but instructions say otherwise
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=166 Summary: Member details form shows yyyy/mm/dd, but instructions say otherwise Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net In either the add new member or update member detail forms, the template says that the date of birth is in dd/mm/yy format, but the displayed value is actually in yyyy/mm/dd format. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 165] New: Crosschecks between member title and sex
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=165 Summary: Crosschecks between member title and sex Product: Koha Version: CVS Platform: PC Status: NEW Severity: enhancement Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net It is currently possible to enter a member with title Ms but sex M, or title Mr but sex F. The CGI script should be able to catch these impossible cases. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 153] opachtdocs and intrahtdocs in koha.conf not initialized
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=153 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 162] Syntax error in newmembers.pl
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=162 a.c.li(a)ieee.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 162] New: Syntax error in newmembers.pl
by bugzilla-daemon＠wilbur.katipo.co.nz 20 Jan '03

20 Jan '03

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=162 Summary: Syntax error in newmembers.pl Product: Koha Version: CVS Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P2 Component: Members AssignedTo: chris(a)katipo.co.nz ReportedBy: a.c.li(a)ieee.org QAContact: koha-devel(a)lists.sourceforge.net newmembers.pl cannot compile; it is missing a closing brace somewhere. The syntax error seems to have been introduced some time after 1.2.2. The newmembers.pl in 1.2.2 looks ok, but not the one in 1.2.3RC23 or the one in the current CVS. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

iso-8859-2 - probelm
by Benedict 19 Jan '03

19 Jan '03

Hi all, I don't know whether this is a Konqueror problem or a Koha flaw...but each time I access this page http://localhost:8080/cgi-bin/koha/members-home.pl Konqueror reverses to iso-8859-1 and polish characters get scrambled. I tried to insert <meta http-equiv=...> tag but to no avail. Isn't there a perl script in Koha that inforces iso-8859-1 everywhere in the "output"? regards, Benedict

5 9

Re: [Koha-devel] Re: A Win32 circulation client (beginning stages)
by Ambrose Li 19 Jan '03

19 Jan '03

Hi, [It seems that you are not cc'ing to the list.] On Sun, Jan 19, 2003 at 08:37:33PM +1300, Patrick Quinn-Graham wrote: > I've started to look at the circulation.pl script (certainly > not the nicest of the perl scripts I've seen in my > life time. Can some one tell me why it has to be _one_ > script? Couldn't there be a borrower_prompt.pl issueing.pl > issuebook.pl that would be way easier to read...) - and lots > of things are pushed through to C4::Circulation::Circ2, so > it could feasibly have a wrapper put around the necessary > functions. Perhaps a WebService? I'm sure you can do those in > Perl. I can't say I like sending things like that over the > HTTP, even if it was going over https. Perhaps I just don't > like programming in that model (open connection, make request, > close connection). yes, Koha's perl code is not very pretty. In 1.3.x Koha is being "templatized" (I mean separating the presentation from the code using HTML templates), and this is not finished yet; and unfortunately circulation.pl is one of those that has not yet gone through "templatization", so it is messier than most other scripts. There are quite a few other important scripts that are still "untemplatized" and thus can't be localized into another language. (Of course by this I don't mean Perl can't do localization any other way, just that the Koha developers had decided on a certain way to localize Koha.) > I'm not really familiar with getting perl to do something over > a network other than through a webbrowser, so I don't know how > much I could help in that regard. If you don't mind working within the existing framework for the moment, then you don't have to worry about knowing how to send things over the network. A CGI-type script doesn't have to directly send things to the network; it only communicates with the web server using an API that involves only sending and receiving through standard input, standard output, and the environment (the CGI "protocol"). With perl you don't even need to worry about the input and the environment. Same thing with communicating with the SQL server; all is done through API's provided by classes. > A shame about the telnet-type-client being broken... > > But then, a lot seems to be broken (using the web-based demo > is kind of tragic, my local copy still gives JavaScript errors > in the catalogue editing section). Could you file a bug report in bugs.koha.org about these JavaScript errors? > My biggest issue right now: authenticating users... how does > Koha do it? I can't quite seem to figure it out just by > looking at the code. I believe the logic is mostly in the C4::Auth module; of course the scripts need to be written a certain way in order for authentication to work. I believe the user names and passwords are in a MySQL table, and at the "browser" level the user sees it as a cookie-based authentication. -- Ambrose Li <a.c.li(a)ieee.org>

3 2