- Koha-bugs - lists.koha-community.org

[Bug 1030] New: handling multiple languages
by bugzilla-daemon＠wilbur.katipo.co.nz 21 Nov '05

21 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1030 Summary: handling multiple languages Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Templates AssignedTo: oleonard(a)athenscounty.lib.oh.us ReportedBy: hany(a)u.library.arizona.edu QAContact: koha-bugs(a)lists.sourceforge.net handling multiple languages is to change the default character setting for the perl / html page to be "unicode". two things: 1. change all the template tag <meta http-equiv="content-type" content="text/html;charset=utf-8"> from charset="iso-...". (to handle multiple languages) 2. make the tag <meta http-equiv="content-type" content="text/html;charset=utf-8"> an include for all the templates so that it is easier to switch for other languages. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1029] in intranet on bookcount.pl missing var in link to item details
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1029 mhafen(a)i.washk12.org changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version| |All ------- Additional Comments From mhafen(a)i.washk12.org 2005-11-18 06:57 ------- Specifically the npl template uses that variable. Should have checked that before posting, sorry. -mhafen ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1029] New: in intranet on bookcount.pl missing var in link to item details
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1029 Summary: in intranet on bookcount.pl missing var in link to item details Product: Koha Version: 2.2.0 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Catalogue AssignedTo: chris(a)katipo.co.nz ReportedBy: mhafen(a)i.washk12.org QAContact: koha-bugs(a)lists.sourceforge.net in intranet/cgi-bin/bookcount.pl add line 94 containing "biblioitemnumber => $bi," Template looks for this variable while building get button labeled Item Details. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1028] New: Couple intranet en template problems
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1028 Summary: Couple intranet en template problems Product: Koha Version: 2.2.0 Platform: PC Status: NEW Severity: normal Priority: P2 Component: Templates AssignedTo: oleonard(a)athenscounty.lib.oh.us ReportedBy: mhafen(a)i.washk12.org QAContact: koha-bugs(a)lists.sourceforge.net Default template: /circ/circulation.tmpl Link to Edit Borrower Line 37 change bornum to borrowernumber npl template: /member/moremember.tmpl Link to add child Line 12 change /cgi-bin/koha/jmemberentry.pl to /cgi-bin/koha/members/jmemberentry.pl /parameters/authorized_values.tmpl Deleting values Line 43 change name=" script_name " to name="script_name" Line 45 change name=" id " to name="id" ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 ------- Additional Comments From cmurdock(a)ccfls.org 2005-11-18 04:16 ------- Okay, that makes sense. Thanks! ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 ------- Additional Comments From chris(a)katipo.co.nz 2005-11-17 11:11 ------- Hmm what i usually do is install a koha, rename the koha.conf file, rename the koha-httpd.conf file and edit it so it points at the correct koha.conf. And then yes install a new version. Although I see no reason why it shouldnt work by just replicating it. I know it will default to /etc/koha.conf unless its told otherwise. I wonder if the SetEnv call is not working? Ahhh ive just realised ... The SetEnv call is passing it through for apache, but if you run a script from the command line, you will need to set it yourself. Sorry I didnt read properly and missed the bit about updatedatabase. if you go export KOHA_CONF="/etc/your.conf" perl -I /path/to/your/modules scriptname then it should run using the right database ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 ------- Additional Comments From cmurdock(a)ccfls.org 2005-11-17 10:36 ------- I have 2.2.4 and HEAD from CVS. That's how I have my koha-httpd.conf set up, too. Did you go through the install process for each of your installations, Chris? Maybe that's where I went wrong. I just copied /usr/local/koha, tweaked /etc/koha.conf and /etc/koha-httpd.conf, and replicated the database, and then did an update from CVS on one of them. Maybe I shouldn't have done it that way, or maybe I did something wrong somewhere. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 ------- Additional Comments From chris(a)katipo.co.nz 2005-11-17 10:16 ------- Which version of koha are you using? Because it seems to work fine in 2.2.3 and prior. On one machine i have 18 koha's running all using different koha.conf files with lines like SetEnv KOHA_CONF "/etc/koha-unido.conf" in my koha-httpd.conf ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 cmurdock(a)ccfls.org changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version| |All ------- Additional Comments From cmurdock(a)ccfls.org 2005-11-17 10:05 ------- Actually, that must not be the only place it's hardcoded. I modified that line, and it still updated my "Koha" database, not the duplicate database I created for use with the CVS version. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1027] New: /etc/koha.conf is hardwired into Context.pm
by bugzilla-daemon＠wilbur.katipo.co.nz 17 Nov '05

17 Nov '05

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1027 Summary: /etc/koha.conf is hardwired into Context.pm Product: Koha Version: CVS Platform: PC Status: NEW Severity: minor Priority: P2 Component: Parameters AssignedTo: paul.poulain(a)free.fr ReportedBy: cmurdock(a)ccfls.org QAContact: koha-bugs(a)lists.sourceforge.net The name of the koha configuration file (/etc/koha.conf) is hardwired into C4/Context.pm. It should instead look at /etc/koha-httpd.conf to find out the location of the koha config file. Under normal circumstances this isn't a problem, but, for example, if you are running multiple versions of Koha (say, a stable one and one from CVS), then if you run the updatedatabase script after doing a fresh CVS update, it can update the wrong database. The line that needs to be changed in Context.pm is line 97. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0