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

Re: I think theres a Bug in new 2.2 Koha release
by Andrés Tarallo 17 Nov '04

17 Nov '04

I don't think so. You must have the following lines added to your virtual hosts configuration: SetEnv PERL5LIB "/usr/local/koha/intranet/modules" SetEnv KOHA_CONF "/etc/koha.conf" please set KOHA_CONF to wherever is your koha configuration file. Hope this helps Andrés PS: There're a few bugs in the context.pm module when you're working under mod_perl. We at ORT are working to fix them, since a greater performance is achieved when working under mod_perl. Harry Jackson wrote: > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 110. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 111. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 112. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 113. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 189. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 190. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 191. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 192. > Global symbol "$context" requires explicit package name at > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue line 193. > > > To fix > > Add the following line: > > my $context = C4::Context->new("/path to/koha.conf"); > > to > > /usr/local/koha/intranet/scripts/z3950daemon/processz3950queue > > The line needs to go before the first use of the $context variable. > Replace "path to" with the directory of where your koha.conf file is. > > Harry

2 2

OPAC ideas
by Owen Leonard 15 Nov '04

15 Nov '04

One thing I think would go a long way towards making Koha's OPAC really great: Right now we've got two really good features in the OPAC: the book basket and virtual shelves (virtual shelves still need some work). What we really need to do, I think, is combine these two things and integrate them better into the OPAC. Users need the ability to convert their book basket to a virtual shelf ("Save as Virtual Shelf") for later use. And users need the ability to reserve all items in their basket or on a virtual shelf. (Librarians should have a similar ability to do bulk reserves for a particular patron from the intranet, but adding the feature in the OPAC is more important). If I had the skills I'd do this myself, but I don't. I really think that making these changes is an important goal, so I hope someone will take this on. -- Owen ---- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

1 0

Opac Manifesto
by Owen Leonard 15 Nov '04

15 Nov '04

There is a wiki up at Librarian.net called OpacManifesto, where people are posting their ideas for the ideal OPAC. It looks like a good place to get ideas (and to see how we're doing so far): http://www.librarian.net/opwiki/index.php?OpacManifesto -- Owen ---- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

1 0

mysql conection problem
by Ernesto Silva - Webmaster 15 Nov '04

15 Nov '04

Hi, we are using koha version 2.1.2 and after some time (the weekend) we can't login with the kohaadmin user. The apache logs claims the following: DBD::mysql::db selectrow_array failed: MySQL server has gone away at /usr/local/koha/intranet/modules/C4/Context.pm line 361. and Context.pm sais: sub preference { my $self = shift; my $var = shift; # The system preference to return my $retval; # Return value my $dbh = C4::Context->dbh; # Database handle my $sth; # Database query handle # Look up systempreferences.variable==$var >>>>>>> $retval = $dbh->selectrow_array(<<EOT); <<<<<<<<<<< 361 SELECT value FROM systempreferences WHERE variable='$var' LIMIT 1 EOT return $retval; } Aparently the database conection is lost, any ideas? WARN: we are using mod_perl !!!! (with quite a performance improvement) Some of the database settings... key_buffer = 64M max_allowed_packet = 1M table_cache = 256 sort_buffer_size = 1M net_buffer_length = 64K interactive_timeout = 240 wait_timeout = 240 myisam_sort_buffer_size = 16M Regards, -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law.

1 0

Bug fix
by Andrés Tarallo 12 Nov '04

12 Nov '04

Today we've been hunting a strange BUG. While doing that we updated the C4 modules from the latest one in the CVS. Our test instlation is 2.1.2 version of Koha. Attached below you'll find a patch with some bugfixes for the Auth.pm module. Maybe calling them bugs is not a good idea, but we took away some annoying messages from the logs. Any feedback is welcome Andres

1 0

Users table
by Ernesto Silva - Webmaster 11 Nov '04

11 Nov '04

hi, what is the "users" table for? is it deprecated? it seems to me that all permissions are managed in the borrower's flags. Regards -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law.

1 0

member-flags.pl patch
by Ernesto Silva - Webmaster 11 Nov '04

11 Nov '04

Hi, We are using Koha version 2.1.2 and we detected that the user flags didn't show up. This is one possible patch. Regards. -- Ernesto Silva - Webmaster - Universidad ORT Uruguay Cuareim 1451. Montevideo. Montevideo - 11100. Uruguay. Email: silva(a)ort.edu.uy "Men and nations will act rationally when all other possibilities have been exhausted." Katz law. --- member-flags.pl.original 2004-11-11 11:28:00.684539200 -0300 +++ member-flags.pl 2004-11-11 12:17:10.340123392 -0300 @@ -58,8 +58,14 @@ $sth->execute($flags, $member); print $input->redirect("/cgi-bin/koha/members/moremember.pl?bornum=$member"); } else { - my ($bor,$flags,$accessflags)=getpatroninformation(\%env, $member,''); - +#---------------------------------------------------------------------------- +# 11-11-2004 - Ernesto Silva (silva(a)ort.edu.uy) - member flags didn't show up +# because getpatroninformation returned a complex "borrower" object not a list. +# More information in: C4/Circulation/Circ2.pm - line 238 + my $bor = getpatroninformation(\%env, $member,''); + my $flags = $bor->{'flags'}; + my $accessflags = $bor->{'authflags'}; +#---------------------------------------------------------------------------- my $dbh=C4::Context->dbh(); my $sth=$dbh->prepare("select bit,flag,flagdesc from userflags order by bit"); $sth->execute;

1 0

[Fwd: [Koha] Koha Docs]
by Stephen Hedges 09 Nov '04

09 Nov '04

Note to developers - I decided to use the GNU Free Documentation License ("copyleft") on these documents, with disclaimer, too. While this may seem like it's overly protective, the copyright belongs explicitly to the author, and he/she can always choose to make it looser later. (Though I think it would be very difficult or impossible to make it tighter later.) Meanwhile, the documents should be free enough for most purposes. I also decided to use version numbering related to the software version, as much as possible. So if a document refers mainly to Koha version 2.0.0, for example, the initial version will be 2.0.0, the first revision would be 2.0.0p1, etc. Many thanks to everyone for the helpful suggestions and information. Stephen ---------------------------- Original Message ---------------------------- Subject: [Koha] Koha Docs From: "Stephen Hedges" <shedges(a)skemotah.com> Date: Tue, November 9, 2004 2:04 pm To: koha(a)lists.katipo.co.nz -------------------------------------------------------------------------- I have begun the process of loading some Koha documents to Sourceforge, which will be the repository for Koha docs until we come up with a better place to store them. Look in koha-doc/en/general and you will find the "official" XML version of Brooke's "Newbie Guide" from the Koha wiki, as well as an HTML conversion of the XML source. Look in koha-doc/en/sysadmin/migration and you'll find the XML and HTML of my "Migrating to Koha" document. I'm working on Nick Rosasco's official Koha Manual (for version 1.2.3) as well as Paul's brochure for version 2.2.0 (in both French and English). I'm open to suggestions for more documents to transfer to XML and load to Sourceforge, so send 'em my way! -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com _______________________________________________

2 1

EU Library Barcode Identification Standard (slightly off-topic)
by Bruffey, Mark 08 Nov '04

08 Nov '04

Our seminary has an extension in Romania. I am attempting to set up a barcode system for the library there. I know that a number of participants this list are in the EU. Is there a standard for library identification by barcode in the EU? If there is, I would like to use that as a model, or try to conform to it. For instance, here in Minnesota, MINITEX assigns a unique combination of the 1st 5 or so digits of barcode to each library in Minnesota. Is there a similar standard in the EU? Sincere thanks for your consideration of this off-topic post. Best, Mark Bruffey, Minneapolis MN.

1 0

Document revision numbering system
by Stephen Hedges 05 Nov '04

05 Nov '04

Hi all - As I am working on moving Koha docs to XML, I would like to start using a uniform system of numbering document revisions. I noticed while working on converting the SGML version of Nick Rosasco's manual that he had numbered the first version as "0.1." So what should I now use for the new XML revision? "0.2" obviously, but what would then justify moving to version 1.0? A google search didn't produce any results that were really helpful. I did see that Gnome documentation is supposed to be numbered according to the version of Gnome that is current. In other words, if a document is produced when Gnome version 1.x is the most current, then that document version starts with "1" and so forth. (For example, the first version of a document produced when Gnome 2.x is the most current would be version 2.0, the next revision would be 2.1, etc., until Gnome version 3.0 is released.) I suppose we could do something similar for Koha. That would change Nick's version 0.1 to 1.0, and the XML version to 1.1, while Brooke's Newbie Guide would be version 2.0 right from the start -- which seems a little confusing to me. Does anybody have any suggestions and/or strong feelings about a document revision numbering system? -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com

4 3