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

Bugs about koha-zebraqueue-daemon ?
by Zeno Tajoli 06 Jul '09

06 Jul '09

Hi to all, as you see in koha general mailing list we are speaking how to setup indexing in production: as I see the solution is not use zebraqueue daemon but to put in cron job rebuild_zebra.pl At 18.14 04/07/2009 pianohacker(a)gmail.com wrote: >Note: The zebraqueue daemon is, to my knowledge, no longer >recommended for reasons > of performance. I know that in my current test, it is slowly > chewing through my memory even with > no actual use (up to a good 143 MB after 2 weeks). As annoying as > the wait for your records > to be indexed is, the rebuild_zebra cronjob is the only viable > option right now. At 09.11 05/07/2009, Chris Cormack wrote: >2009/7/5 Jonson philip <superjojo1000(a)gmail.com>: > >The daemon hasn't been kept up to date, and has some issues with >memory leakage, so on all systems you should run rebuild_zebra.pl as a >cron job. for my library is not a good solution. We want to use Authority a lot in cataloguing and we need to insert a new authority record and immediatly use it. So in fact I need to fix zebraqueue daemon !! There are in bugzilla description of this bug ? Could you send me a description of the bug ? More descriptions, more easy to fix it. Cheers Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

[Koha] barcodes,
by Chris Nighswonger 04 Jul '09

04 Jul '09

On Sat, Jun 27, 2009 at 4:27 PM, Chris Nighswonger < cnighswonger(a)foundations.edu> wrote: > On Sat, Jun 27, 2009 at 8:10 AM, mike re-v<mrmrmr50(a)yahoo.com> wrote: > > > > Greetings, > > print to file and send it to me, I'll see if I can open it. > > Alternatively, hexedit will open, it and it could look at the leader > > and the end byte codes to see what it is you are producing.Then compare > what you are producing to what works. > > > > from the command line $ hexedit foo.pdf > > > > Alternately you can just open the pdf in a plain text editor and check > to see that the barcode data is there. PDF is a sort of mangled Post > Script stream. > > > Below is the stream for a single item. The line with the series of > zeros and ones is the barcode. However, I can confirm that the > barcodes do not display in Reader 9.0 while they do in 7.0. Versions > 8.0 and 9.0 use PDF version 1.7 while 7.0 uses 1.6. There may be a > subtle difference in syntax that causes the breakage. I'll open a bug > and try to take a look at it next week. > The issue here is not a Koha issue, but *probably* an issue where Adobe Reader does not maintain backward compatibility. Fortunately the fix is not so bad. We just switch from embedding the barcodes as a Type3 font to graphical embedding. I'll submit a patch later today against the current HEAD. It will need to be back-ported to the 3.0.x branch as well. Regards, Chris

2 3

Apache bandwidth tuning in default config
by Tomás 03 Jul '09

03 Jul '09

I've been playing recently with some firefox extensions for web developers: FireBug: https://addons.mozilla.org/es-ES/firefox/addon/1843 PageSpeed: http://code.google.com/intl/es-ES/speed/page-speed/index.html YSlow: http://developer.yahoo.com/yslow/ and found that enabling certain options in the koha's apache VirtualHosts configuration would improve a lot koha's performance in bandwidth use. Only the opac startup page bandwidht usage goes from 368.5K to 118.3K. Enable http compression using mod_deflate --------------------------------------------------------------- Document this command for enabling this in Debian/Ubuntu # a2enmod deflate and add this lines to koha-http.conf in both VirtualHost definitions SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip I specify not to apply useless compression to compresed images. Further options could be used. See http://httpd.apache.org/docs/2.0/mod/mod_deflate.html Enable better caching features by setting explicit expiration far in the future for static content using mod_deflate ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Document this command for enabling this in Debian/Ubuntu # a2enmod expires and add this lines to koha-http.conf in both VirtualHost definitions ExpiresActive On ExpiresDefault "modification plus 1 year" as mod_expires only applies to files in the filesystem it is safe to rely on modification date. This could be fine-tuned, for example on a per filetype basis (see http://httpd.apache.org/docs/2.0/mod/mod_expires.html) ----- PageSpeed in particular offers some recommendation on image sizes and provides an optimal image file for substitution. This could be analised. To+. -- Aparición con vida de Jorge Julio López.

1 0

July #koha IRC meeting transcript
by Galen Charlton 01 Jul '09

01 Jul '09

Hi, Thanks to everybody who participated today. A transcript of the meeting can be found at http://koha.org/cgi-bin/logs.pl?user=&startdate=2009070112%3A00%3A00&enddat… Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 0

Wide character error
by C W Nel 01 Jul '09

01 Jul '09

I staged a record and it imported 100%. I can view it and can see a diacritic (650 7 _aHuérfanos) This record cannot be saved/edited. It gives the “Wide character” error. If I delete the field, it saves 100%. It is obvious that it is not a mysql problem, because it was imported correctly into the database. I tried my best to configure everything to be utf-8, but obviously something is wrong. Can someone please advise? Thanks

1 0

hypertext link
by C W Nel 01 Jul '09

01 Jul '09

Is there an easy way to link a record to a specific URL? With other words to have a hyperlink on a specific record to take you to e.g. an html or pdf file to supply more info on this record? Thanks for any help.

4 6

Reminder - general project IRC meeting 1 July 2009
by Galen Charlton 30 Jun '09

30 Jun '09

Hi, The next general meeting of the Koha project will be held on the #koha IRC channel at 19:00 UTC+0. The following standing agenda items will be discussed: 1. Koha 3.2 update 2. Koha 3.0.x update 3. Actions from the previous IRC meeting 4. Addition of “Skip to content” links in the staff client, as discussed on Koha-devel [1] To suggest additional agenda items, please go to the wiki page for this meeting located at <http://wiki.koha.org/doku.php?id=meetingnotes09jul01>. [1] http://lists.koha.org/pipermail/koha-devel/2009-June/009733.html Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

3 2

Re: [Koha-devel] [Koha] Saving MARC records very slow
by Mason James 30 Jun '09

30 Jun '09

On 2009/06/30, at 11:52 AM, Rick Welykochy wrote: > Cab Vinton wrote: > >> This was covered on the list a while back -- in Firefox it was taking >> 40-50 s on our staff clients to save records. >> >> We've switched to Google Chrome & the time is now much more >> manageable. >> >> I don't believe a diagnosis or fix were ever found for the Firefox >> issue. > As pointed out, this is because of Javascript. > > Question: can Koha operate properly with JS disabled? If not, why not? > > Observation: JS is quite slow compared the server itself. Perhaps the > *HUGE* task of validating a MARC save could be (optionally) left to > the server to validate. this is a good suggestion, but might require a pretty big rewrite of the marc-editor code (not for the faint-hearted) another easier speed win could be to find the slow/often-executed JS code thru profiling, and rewrite it with some optimised jquery is jquery code faster? ermmm i'm not sure actually ;) just a thought...

1 0

updateitem.pl
by Roche III, Edward 29 Jun '09

29 Jun '09

Can someone tell me how to use this script. I know it cannot be used from the command line and I have tried to run it from with the browser. Any help help would be great. Thanks Ed Edward J. Roche Network Administrator Solanco School District 717.786.2151 x2437 "At the End of the Day, Did You Play to Win or Not to Lose?"

6 8

koha 3.0 - inexistant table 'borrower_attributes' during update
by Frère Sébastien Marie 29 Jun '09

29 Jun '09

I have a problem when I update koha, during last stage (database update in webinstaller). KOHA Version: 3.0 (git track origin/3.0.x) update 0f6359539cd3a16d28537b18d3c23447b0cd17fb to b2a4853fc53c471664a54630b783c9cc7ac4f93f Database version: update 3.00.01.007 to 3.00.02.012 --- webinstaller log --- [Mon Jun 29 16:11:59 2009] updatedatabase.pl: inside 3.00 at koha/installer/data/mysql/updatedatabase.pl line 1963. [Mon Jun 29 16:11:59 2009] updatedatabase.pl: DBD::mysql::db do failed: Table 'koha.borrower_attributes' doesn't exist at koha/installer/data/mysql/updatedatabase30.pl line 248. [Mon Jun 29 16:11:59 2009] updatedatabase.pl: DBD::mysql::db do failed: Table 'koha.borrower_attributes' doesn't exist at koha/installer/data/mysql/updatedatabase30.pl line 249. --- end --- --- part of "koha/installer/data/mysql/updatedatabase30.pl" --- +$DBversion = "3.00.02.005"; +#$DBversion = '3.01.00.010'; +if ( C4::Context->preference('Version') < TransformToNum($DBversion) ) { + $dbh->do("ALTER TABLE `borrower_attributes` MODIFY COLUMN `attribute` VARCHAR(64) DEFAULT NULL"); + $dbh->do("ALTER TABLE `borrower_attributes` MODIFY COLUMN `password` VARCHAR(64) DEFAULT NULL"); + print "Upgrade to $DBversion done (bug 2687: increase length of borrower attribute fields)\n"; + SetVersion ($DBversion); +} --- end --- --- patch GIT --- commit c1901a84aeaee55a8590d64f8ee1fcac328cf264 Author: Henri-Damien LAURENT <henridamien.laurent(a)biblibre.com> Date: Wed May 6 15:42:19 2009 +0200 UpdateDatabases for 3.0.2 updating elements in order to make 3.0.2 work Signed-off-by: Henri-Damien LAURENT <henridamien.laurent(a)biblibre.com> --- end --- Shortly, updatedatabase30.pl tried to update 'borrower_attributes' table, but this table doesn't exist in my version... (koha 3.0) This modification (the part that failed) is for bug 2687 (increase the length of the password field to VARCHAR(64)). I think is a bug correction for koha 3.1, but not for 3.0 (I hope for my database... else where is my 'borrower_attributes' table ?) Should I ignore this error, with no problem for data integrity (in futures updates) ? Thank. -- Frère Sébastien Marie Abbaye Notre Dame de La Trappe 61380 Soligny-la-Trappe http://www.latrappe.fr/

1 0