Re: [Koha] Issue Report

Dear Mr Waqar Aslam Please find below the Sql Reports as desired. As this version is too old i recommend to use the latest version of koha or please contact with me for the latest Full Stack Latest version koha live DVD. Please copy and past the following command in SQL box. SELECT

[Koha] koha authorities

I have been trying to run the koha-auth facility that is supposed to generate authority records. See below error from my code inveniouser@inveniosrv:~/.cpanm/work/1439883119.26275/Koha-Contrib-Tamil-0.040/share/etc$ sudo koha-auth create_from_biblio

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/data/mysql/updatedatabase.pl;h=950ed2067dac0edd51cf5e49ff25862c6f53ecdb;hb=refs/heads/3.20.x#l10576 It exploded because you already had the constraint (course_reserves_ibfk_2), so everything is fine. 2016-01-11 17:01 GMT+00:00

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

Correction: It comes from bug 14205 which has been pushed to 3.18.x and 3.20.x, so you already have the constraint (but double check!). You can also forget this one :) 2016-01-11 16:24 GMT+00:00 Jonathan Druart : > Hi Gary, > >> DBD::mysql::db do failed:

Re: [Koha] Koha upgrade 3.18.11 --> 3.20.07

Hmmm... Using "SHOW CREATE TABLE course_reserves" returns... . . . PRIMARY KEY (`cr_id`), UNIQUE KEY `pseudo_key` (`course_id`,`ci_id`), KEY `course_id` (`course_id`), KEY `course_reserves_ibfk_2` (`ci_id`), CONSTRAINT `course_reserves_ibfk_1` FOREIGN KEY (`course_id`) REFERENCES

[Koha] Koha upgrade 3.18.11 --> 3.20.07

I am seeing two MySQL errors thrown when trying to update from 3.18.11 --> 3.20.07. Are these benign or something about which concern should be raised? The installation here is Ubuntu 14.04.3 with a multi-tenant package install of Koha. Mysql Ver 14.14 Distrib 5.5.46, for debian-linux-gnu

Re: [Koha] [Koha-bugs] [Bug 15547] New: Location for stored OPAC header images

I'm responding here to a bug report because I think it's more of a support issue. > We are currently customising our OPAC page and notice that Koha requires > images > to be stored at an https: address. Please could you advise how and where I > should upload these images so that they can be