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

Premature end of script headers
by Rick Welykochy 14 Sep '07

14 Sep '07

Hi all, Directly related to our discussions about error handling, I am in a fix. I have installed a new instance of Koha/2.0.0 (don't ask!) and get the following error at the OPAC login URL, e.g. http://HOSTNAME/cgi-bin/koha/opac-main.pl 500 INTERNAL SERVER ERROR So I look in the opac error_log: ==> log/opac-error_log <== [Fri Sep 14 15:58:59 2007] [error] [client 10.11.12.8] Premature end of script headers: opac-main.pl Hrmmm .... now what? Ah yes, let's try that script from the shell: 1. set PERL5LIB as required 2. run the script: # perl opac/cgi-bin/koha/opac-main.pl Set-Cookie: sessionID=; path=/ Date: Fri, 14 Sep 2007 06:03:58 GMT Content-Type: text/html; charset=ISO-8859-1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> <html> etc.etc.etc. So this script runs fine in the shell but not in Apache. And in Apache, the error is so severe I see no error message. I retried after adding use CGI::Carp qw(fatalsToBrowser); to the script, to no avail. I also repeated this experiment using the about.pl, since that script is so simple. Same results: shell 1 apache 0 Anyone have any clues? I am using my knowledge of Koha/2.2.9 to guide me so perhaps Koha/2.0.0 needs a slightly different configuration in Apache?!?! cheers rickw -- _________________________________ Rick Welykochy || Praxis Services Traditionally, most of Australia's imports come from overseas. -- Keppel Enderbery

2 2

Re: FAQ: Why am I prompted to save a .pl file? was: Problems adding a biblio...
by Rick Welykochy 14 Sep '07

14 Sep '07

MJ Ray wrote: > Hennie Rautenbach <hennie(a)sabinet.co.za> wrote: [...] >> trying to add a "biblio" manually. We are prompted to save the >> "addbiblio.pl" file. I see this has happened to other users before >> (google search), but I am unable to find a reference to a fix for it. > > This has happened because the script has crashed without producing any > output, so apache has guessed (incorrectly) what headers to send and > your browser interpreted it as a file download. > > To stop it, fix the crash. To fix the crash, find out the error. To > find out the error, look in koha-error_log for the time of the crash. > (To find koha-error_log, see the ErrorLog line in koha-httpd.conf) The developers can go a long way towards stopping this situation from every happening again. To stop this problem once and for all from ever occurring again, catch all errors. To catch all errors and thus produce the correct headers for EVERY Koha script, use exception handling. Works a treat :) cheers rickw -- _________________________________ Rick Welykochy || Praxis Services The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place. -- Douglas Adams on Windows '95.

4 11

Code Cleaning : Authorities.
by Henri-Damien LAURENT 13 Sep '07

13 Sep '07

Those first two are the main reason I am writing. Does anyone still use thesaurus.pl ? Considering that now frameworks allow to link Authorities with one another, I think we should drop linker down. One problem is : All linking and hierarchy code is UNIMARC and hardcoded. I would like to allow more versatility on this. But this would require those new system preferences : relation type subfield (UNIMARC 2) relation authnumber subfield (UNIMARC 3) relation authtype subfield (we should agree on using authtypes or authtypecode as value in those subfields) (UNIMARC 5) relation tag (UNIMARC 550) child flag (UNIMARC f) mother flag (UNIMARC "g") Plus would require some little modifications of auth_finder to enable relation Choice. Maybe it could interesting to enable multiple authority link for a field. This would only require to manage a list of authorities to search in. We reviewed the AuthoritiesMARC code with Paul. And thought that unification between Authorities.pm and Biblio.pm was not a worth the work. a) Authorities search is much different from biblio search. b) inner tables differs so that it would oblige us to make heavier functions. So Authorities Will stay as such. While Code cleaning it, some questions remains. GetSummary as well as Buildhererarchies is still quite customer dependant and used for display. But it Hardcodes some HTML preprinting. So that when people want This or that display, one has to modify a C4/AuthoritiesMARC. For instance : One wants that term list are displayed : /Heading/ BT /Broader Term/ NT /Narrower Term/ UF /Used For/ /Comments./ Another wants that term list are displayed : /Heading/ TG /Broader Term/ TS /Narrower Term/ EP /Used For/ Comments : /Comments/. Another wants only Heading$a -- Heading$b -- Heading$z And we have to make little changes to the code and then upgrading process is harder. Solution ? A) Using xslt ? B) using HTML::Template to "simulate xslt" Then ppl would only have to modify template for summary processing "mini" template on each record. C) keeping this as such. This would also be helpful in getting information for search resultlists in biblios more user adapted. Comments welcome. -- Henri-Damien LAURENT

3 2

Introduction
by Deb Bergeron 13 Sep '07

13 Sep '07

Good Morning! After joining your list I realized many folks introduce themselves. Forgive me for *lurking* without saying 'hello.' I'm Deb Bergeron and a complete newbie to the open-source community. I'm currently a System Admin--User Support for our III ILS system for CLIC, <http://clic.edu> an academic consortium with 8 libraries and 6 branches--all independent. My background is in Web development, telecommunications, and technical writing. I've been in LibraryLand for 5 years. My professional library experience began as a librarian in an all-male federal prison in PA where I developed an ILL program with the public and academic libraries. I've completed 50% of my MLIS. I live as green as I can, and currently study edible weeds, as well as some programming languages. All of my contact information is below. Deb -------------------------------------------------------------------------- Deb Bergeron <mailto:bergeron@macalester.edu> CLIC <http://clic.edu>, System Administrator User Support 1619 Dayton Ave. Suite 204A, Saint Paul, MN 55104 T: 651.644.3878 C:651-487-7609 F:651.644.6258 <mailto:bergeron@macalester.edu>

1 0

koha 2.2.9 for ubuntu 6.10 (CMARC)
by long_sam.tw 12 Sep '07

12 Sep '07

Hi,Koha Develop team I'm come from Taiwan ROC. I package koha 229 for ubuntu 6.10. 1. Default MARC for CMARC 2. fix z3950 for CMARC (CCCII) for Taiwan 3. Default Template is NPL 4. update CCCII to UNICODE MAP (Encode::HanExtra),thank Audrey Tang to help it. 5. I translate Install.pm for chinese(for taiwan) 6. I provide two types about simple cmarc & full cmarc . 7. If you have to proxy,I suggest to set up before install koha. 8. Install process, you have to set your cpan server, and then you only press enter key. simple-cmarc http://groups.google.com.tw/group/kohataiwan/web/koha-2.2.9-simple.tar.gz full-cmarc http://groups.google.com.tw/group/kohataiwan/web/koha-2.2.9-full.tar.gz please commit themes. enjoy koha laxendion ____________________________________________________________________________________ 設定安全圖章，保護您的 Yahoo!奇摩帳號不被駭客盜用！ http://tw.info.yahoo.com/seal/index.html

1 0

Koha Database Structure Meeting
by Joshua M. Ferraro 12 Sep '07

12 Sep '07

Hi all, Paul and I have done some cleaning of the kohastructure.sql file for the 3.0 release lately (see the following commitdiffs: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commitdiff;h=d60d540d6db582… http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commitdiff;h=b40c26cffedf10… ). There are still a few remaining issues to clear up so we've decided to hold a meeting strictly about the Koha SQL definition for 3.0. The meeting's open to anyone interested in database design, feel free to join us on August 31st at 16:00 GMT. Here's the time in your area: http://tinyurl.com/2bteuw We'll be meeting on IRC at irc.katipo.co.nz on channel #koha, though you can also reach us via the freenode relay on #koha at freenode. I've put up a meeting agenda, please feel free to add to it: http://wiki.koha.org/doku.php?id=meetingnotes07aug31 Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

3 4

vmware image of the 2.2.9 version of Koha
by Deb Bergeron 12 Sep '07

12 Sep '07

Hi, Is anyone aware of a vmware image of the 2.2.9 version of Koha? Thanks, Deb -------------------------------------------------------------------------- Deb Bergeron <mailto:bergeron@macalester.edu> CLIC <http://clic.edu>, System Administrator User Support 1619 Dayton Ave. Suite 204A, Saint Paul, MN 55104 T: 651.644.3878 C:651-487-7609 F:651.644.6258 bergeron(a)macalester.edu <mailto:bergeron@macalester.edu> http://clic.edu

2 1

Interface Design Patterns
by Joshua M. Ferraro 06 Sep '07

06 Sep '07

Hi all, Owen Leonard and I have been working on improvements to the organization, markup, and style of the Koha 3.0 templates. I just want to summarize our progress thusfar. 1. We've been primarily working on the Staff client as the OPAC had a fairly massive overhaul recently and we're pretty confident we've solved most of the design problems there and can easily apply those styles to the 3.0 OPAC at any time. 2. we moved all the non-.inc files out of the includes/ directory, and moved all the .tmpl files into a modules/ directory. We also created a lib/ for external libraries such as YUI, Jquery, the calendar library. CSS and JavaScript are now contained in the css/ and js/ dirs respectively. 3. We've started working on a 'style guide' for Koha templates that is a collection of recommended conventions, background on organization of the templates, and a discussion of 'patterns', 'idioms', and other UI terminology and concepts: http://wiki.koha.org/doku.php?id=en:documentation:templates_style_guide 4. Started organizing the Koha pages into categories based on the 'pattern' of the page. For instance, there are two pages with a type of 'login' (the installer login page and the main auth.tmpl). Many many pages in Koha fall into the pattern of 'form + filter', and we've laid out the common elements and will be defining conventions for how the markup and style will work for the default 3.0 templates. More patterns will follow as we identify and define conventions for them. 5. We're validating pages as we go, with the goal of having all pages completely valid in 3.0 as they are in 2.2. That's about all I can think of at the moment ... we're meeting again tomorrow to continue along this track, and I'll report back here as we make progress. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

database analysis (diff between 22+updatedatabase and kohastructure.sql)
by Paul POULAIN 04 Sep '07

04 Sep '07

I have reviewed all the diffs between my ipt3 database, that is a koha 2.2 + updatedatabase and the head (3.0) kohastructure.sql There are lots of varchar/char differences =============================================== http://dev.mysql.com/doc/refman/5.0/en/silent-column-changes.html says : Before MySQL 5.0.3, VARCHAR columns with a length less than four are changed to CHAR. OK, my database was on mySQL 4.1 previously, thus the differences. I discard them, it's meaningless anyway There are a lot of NOT NULL default '' vs NOT NULL ================================================== (or NOT NULL default 0 vs NOT NULL) http://dev.mysql.com/doc/refman/5.0/en/data-type-defaults.html says : If the column cannot take NULL as the value, MySQL defines the column with an explicit DEFAULT clause, using the implicit default value for the column data type. Implicit defaults are defined as follows: For numeric types, the default is 0, with the exception that for integer types declared with the AUTO_INCREMENT attribute, the default is the next value in the sequence. For date and time types other than TIMESTAMP, the default is the appropriate “zero” value for the type. For the first TIMESTAMP column in a table, the default value is the current date and time. See Section 10.3, “Date and Time Types”. For string types other than ENUM, the default value is the empty string. For ENUM, the default is the first enumeration value. So the differences as meaningless, I discard them as well. (hereafter, when I write x VS Y, I mean kohastructure.sql VS mydatabase) action_logs : text vs mediumtext : ================================== just differ on the length the record can contain, but even text is enough (http://dev.mysql.com/doc/refman/5.0/en/storage-requirements.html) biblioitems ============ - volumedesc is text VS char(255). Harmless, text is better (although more space consuming) - some columns (the new ones) are not at the same place in the table. harmless - marc longblob vs blob : marc column is deprecated & could be dropped soon if I don't mind. howeber, longblob is better browser ======== don't exist VS exist : this table is speficically created & filled by a specific script, I'll explain on request what it is for categorytable ============== text VS mediumtext : harmless, anyway, text is too large imho charges ======== don't exist VS exist : kohastructure is right. we can drop it. deletedbiblioitems ==================== dewey 8,6 VS char(30) : kohastructure must be modified to char(30), as in biblioitems. deleteditems ================ barcode char(9) VS char(30) : kohastructure must be modified to char(30), char(9) is too small for some libraries items ================= homebranch : char(4) VS char(10) : this one is a major diff, that can cause bugs. ***MUST*** be changed in kohastructure, or contraints will fail. itemsprices ============= don't exist VS exist : kohastructure is right. we can drop it. labels ============== - batch_id exist VS don't exist : kohastructure probably right. - ENGINE=myISAM VS ENGINE=InnoDB : MUST be changed in kohastructure labels_conf : =============== - lot of differences : my structure has to be updated (however, ipt don't use label facilities, so they don't care ;-) ) - ENGINE=myISAM VS ENGINE=InnoDB : MUST be changed in kohastructure labels_templates : =================== table has to be added on my side letters & many other tables ========== mediumtext VS text : harmless, both are acceptable. mediumtext maybe a little bit better although marc_biblio ============ can be dropped on my side, I agree mediatypetable : ================= exist VS don't exist : i'm right imho, kohastructure should drop this table sessionqueries =============== don't exist VS exist : kohastructure is right. we can drop it. subcategorytable ================= exist VS don't exist : i'm right imho, kohastructure should drop this table subscription ============== firstacquidate : NULL default NULL vs NOT NULL. hdl will confirm, but I think NOT NULL is better here subscriptionhistory ============== histstartdate : NULL default NULL vs NOT NULL. hdl will confirm, but I think NOT NULL is better here users/websites / z3950queue/ z3950queries =============== don't exist VS exist : kohastructure is right. we can drop them Foreign keys ============== on my side most constraints are repeated, I don't know why, but it's stupid As a conclusion : I should do that test again on another 22+updatedatabase config, to be sure, but it seems there are no so many diffs between kohastructure.sql & 22+updatedatabase. I'll let you know ASAP -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

1 0

Testing Koha 3
by Bradley Duane Peters 03 Sep '07

03 Sep '07

Hello, I'm aware that Koha 3 is not yet even in beta, but I'd be interested to know whether its at the point were it can be run. I have also looked at the Roadmap on the wiki but at this point I'm not familiar enough with the codebase to interpret that properly. I did the basic checkout from the public Git repository and have been looking at that. It's very possible I've missed it because I'm not very familiar with Koha but I can't find any of the zebra database stuff. In short, is it possible to setup an instance of Koha using the code from the repository? And, if so is there somewhere in particular I should be looking for help? Thanks, Bradley Peters.

3 3