Re: [Koha] Unable to install Koha on Ubuntu

[Quỳnh Vũ Đỗ]

Hi,
My order of installation is the following:
1) Install the Server operating system (Ubuntu, Debian)
2) Install the Web server software (e.g. Apache 2), PHP and Database server
(MySQL or MariaDB). You may need to do some configuration for Apache and
for authentication with MySQL (or MariaDB ?)
3) Install koha (you need to add the repository first)
4) Configure Apache for listening to Koha instances
5) Install Koha via the web installer or regenerate an existing Koha
instance by SQL (then updating the database schema and zebra index)

For step 2 (I use Ubuntu and MySQL), I usually follow the complete
procedure described in this tutorial:
https://www.digitalocean.com/community/tutorials/how-to-install-linux-apache-mysql-php-lamp-stack-ubuntu-18-04
(you may choose from the drop down menu Ubuntu 20.04).
I also install phpmyadmin on experimental Koha servers.
For steps 3, 4, 5 I follow the Koha wiki page on installing Koha for Ubuntu
(https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages)

I did it without problems for Koha 19.xx and 20.05 on Ubuntu 16.04, Ubuntu
18.04 and 20.04 (on experimental servers)

Hope that helps.

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 4, 2 thg 12, 2020 vào lúc 23:19 takan bhatt 
đã viết:

> I am from Vapi Gujarat. We were trying to install koha on Ubuntu 20.04.
> After installing koja common, adding intraport 8080, I proceed for
> installing mariadb but there was some error in some focal. I check
> documents on internet and tried again with Ubuntu 18.04 but in both the
> cases I failed. Then I installed Debian 9 and was able to install Koha
> successful but debian is running slow and there are issues of running other
> software like any desk on Debian.
>
> Kindly guide me properly bcoz I did many installations for koha 18 to 19
> and I never face any problem. Even I have installed koha on cloud too. But
> this time some documentation might have changed.
>
> Please help me
>
> Rajesh Bhatt
> Vapi
> Gujarat
> India
> Whatsapp :  9824925609
>
> On Wed, Dec 2, 2020, 8:27 PM Coehoorn, Joel  wrote:
>
> > When we did this last year for 18.04 (20.04 didn't exist yet), we had to
> > use MariaDB instead of MySql, but otherwise everything went pretty much
> > according to the wiki guides for the package installer.
> >
> > Joel Coehoorn
> > Director of Information Technology
> > York College of Nebraska
> >
> >
> > On Wed, Dec 2, 2020 at 3:49 AM Jonathan Druart <
> > jonathan.dru...@bugs.koha-community.org> wrote:
> >
> >> Hello,
> >> Which problems did you face when you tried with Ubuntu?
> >> About the slowness, go to the about page and make sure you don't see
> >> any warnings there.
> >> Regards,
> >> Jonathan
> >>
> >> Le mer. 2 déc. 2020 à 10:25, takan bhatt  a
> écrit
> >> :
> >> >
> >> > Dear Sir/ Madam
> >> >
> >> > I am trying to install Koha on ubuntu. in this process there are some
> >> > problems while installing mariadb. I have tried both with Ubuntu
> 20.04 &
> >> > 18.04 but faced the same error. Finally I installed Debian 9.
> Everything
> >> > was fine. Koha installed but system is running very slow.
> >> >
> >> > Kindly guide me.
> >> >
> >> > Rajesh Bhatt
> >> > ___
> >> >
> >> > Koha mailing list  http://koha-community.org
> >> > Koha@lists.katipo.co.nz
> >> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >> ___
> >>
> >> Koha mailing list  http://koha-community.org
> >> Koha@lists.katipo.co.nz
> >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
> >>
> >
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] some documentation (19.11 and 20.05) pages are slightly outdated

[Quỳnh Vũ Đỗ]

Hello
I have been using Koha documentation to extend Koha 19.11 as a CMS and
followed instructions given on the following page:
https://koha-community.org/manual/19.11/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms

*Under the section "Editing the pages template" it is written as follows:*
- Copy /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/
opac-main.tt to /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/
pages.tt
- Edit /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/en/modules/pages.tt
- At approximately line 61, change this:
[% IF ( OpacMainUserBlock ) %][%
OpacMainUserBlock %][% END %]
- To this:
[% IF ( page_test ) %][% page_test %][%
END %]

*But in the pages.tt  file (copied from opac-main.tt
) and where modifications are to be carried out, the
line shows not at approximately line 61 but at line 152 and is written as:*
 [% IF ( OpacMainUserBlock ) %][%
OpacMainUserBlock | $raw %][% END %]

It is of course a very minor difference but for the sake of exactitude, it
would be nice to have these differences corrected (line number and code)

*There is however a bigger issue with the following content:*

Remark: You may wish to disable your News block of these CMS style pages
e.g. when you do not want it displayed on the CMS style pages or where the
News block is long enough that it actually makes the ‘page_test’ include
scroll outside the default viewport dimensions. In that case, remove the
following code from your pages.tt template.

[% IF ( koha_news_count ) %]


[% FOREACH koha_new IN koha_news %]
  [% koha_new.title %]
  [% koha_new.new %]
  (published on [% koha_new.newdate
%])
[% END %]


   [% END %]


*Because the code to be researched as above has been completely modified
and spans from line 72 to 102 (30 lines of code) and even further.*

The same remarks stand also for 20.05 documentation (
https://koha-community.org/manual/20.05/en/html/extending_koha.html#using-koha-as-a-content-management-system-cms
)

To whom shall we report this, else than in this mailing list?

Kind regards
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Order and number of news appearing in OPAC

[Quỳnh Vũ Đỗ]

Hello,
We are using 19.11.06 (close to production)  and 19.11.09 (for testing),
under Ubuntu 18.04 LTS.
We have the following problems in displaying news on the OPAC home page (
opac-main.pl):

1) When the field "Number" of the news item is not set, the news are
displayed in increasing id number on the OPAC, i.e. the oldest new comes
first and the newest new item comes last, at the bottom of the page. Is
there a way to reverse the order? I.e. last news on top and oldest news at
the bottom of the OPAC home page?

2) Also, all the news (not flagged as expired) do appear. Thus, if you have
like tens of news, there will be a very long page. Is there a way to limit
the number of news displayed? For example only the latest news? With an
optional link to show all the news.

Or is there a way to display only the clickable title of the news so that
clicking on the title would open the news item for reading?

Displaying all the news (when there are many and when you do not wish to
flag them as expired right away) pushes the content of OpacMainUserBlock
down so that the coverflow (which BTW we did not yet succeed to make it
work) is down far away from sight of visitors

In last resort it would be necessary to modify the code of opac-main.pl

Thanks in advance for any hint or insight on these issues.
Kind regards
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Using News in 20.05

[Quỳnh Vũ Đỗ]

Hello
I fixed the problem.
I was confused between the two languages interfaces (En and vi-VN). Indeed,
I had to create two similar new entries, one with display location as
opacheader (en) and the other one as opacheader (vi-VN) to get my banner
displayed on both language interfaces.
Best regards

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 3, 15 thg 9, 2020 vào lúc 23:13 Quỳnh Vũ Đỗ <
quyn...@thanglong.edu.vn> đã viết:

> Hello
> I am studying the use of Koha. I started with Koha 19.11 under Ubuntu
> 16.04 LTS. Koha has been upgraded to version 20.05.03.
>
> Information that was before put in OpacMainUserBlock has now been
> transferred to some news item. When I want to edit news item, under the
> drop-down menu I now have the following choices:
> All
> Librarian interface
> Slip
> en (English language interface)
> OPAC News (en)
> OpacNavRight (en)
> opacheader (en)
> OpacCustomSearch (en)
> OpacMainUserBlock (en)
> opaccredits (en)
> OpacLoginInstructions (en)
> vi-VN (Vietnamese language interface)
> with same entries as under English language flagged as vi-VN
>
> Now I have a graphic banner for the library which in version 19.11 was in
> the field opacheader under Koha Administration/Global System
> Prefereneces/OPAC. It has now moved in 20.05 to the news with display
> location opacheader (vi-VN) with the following content:
> 
>
> However, the link is broken as the banner image does not appear other than
> as a "broken image" in the News table and when I reload the OPAC home page
> I can't see any banner image either.
>
> When I look at the source code of the OPAC home page I can see the
> following code:
>
>  class="opacheader_vi-VN_body"> src="/opac-tmpl/bootstrap/images/banner.png" style="width: auto; height: 
> auto;" /> 
>
> However, if I click on the img src link on the OPAC home page source code,
> I effectively can display the banner.png image. So although the link looks
> correct but the image doesn't show up on the OPAC page. Does somebody know
> how to fix that link problem?
>
> Besides, this graphic banner should appear in opacheader (en) as well as
> in opacheader (vi-VN). I figured to do that would require to create two
> identical news entries, one displayed in opacheader (en) and the other one
> in opacheader (vi-VN)? Am I right?
>
> It seems with 20.05 that you can have either to display a news item
> everywhere (all) or only in a single location, not two locations?
>
> Any hints and explanation would be appreciated. Thanks for reading.
> Best regards
> Quynh
>
> Thanks
>
> =
> M. Vũ Đỗ Quỳnh (Ph.D)
> Trường Đại học Thăng Long - Université de Thang Long - Thang Long
> University (Hanoi, Vietnam)
> Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
> internationale - Vice-Rector in charge of International Cooperation
> Web: http://thanglong.edu.vn/
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Using News in 20.05

[Quỳnh Vũ Đỗ]

Hello
I am studying the use of Koha. I started with Koha 19.11 under Ubuntu 16.04
LTS. Koha has been upgraded to version 20.05.03.

Information that was before put in OpacMainUserBlock has now been
transferred to some news item. When I want to edit news item, under the
drop-down menu I now have the following choices:
All
Librarian interface
Slip
en (English language interface)
OPAC News (en)
OpacNavRight (en)
opacheader (en)
OpacCustomSearch (en)
OpacMainUserBlock (en)
opaccredits (en)
OpacLoginInstructions (en)
vi-VN (Vietnamese language interface)
with same entries as under English language flagged as vi-VN

Now I have a graphic banner for the library which in version 19.11 was in
the field opacheader under Koha Administration/Global System
Prefereneces/OPAC. It has now moved in 20.05 to the news with display
location opacheader (vi-VN) with the following content:


However, the link is broken as the banner image does not appear other than
as a "broken image" in the News table and when I reload the OPAC home page
I can't see any banner image either.

When I look at the source code of the OPAC home page I can see the
following code:

 

However, if I click on the img src link on the OPAC home page source code,
I effectively can display the banner.png image. So although the link looks
correct but the image doesn't show up on the OPAC page. Does somebody know
how to fix that link problem?

Besides, this graphic banner should appear in opacheader (en) as well as in
opacheader (vi-VN). I figured to do that would require to create two
identical news entries, one displayed in opacheader (en) and the other one
in opacheader (vi-VN)? Am I right?

It seems with 20.05 that you can have either to display a news item
everywhere (all) or only in a single location, not two locations?

Any hints and explanation would be appreciated. Thanks for reading.
Best regards
Quynh

Thanks

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Coverflow installation problems

[Quỳnh Vũ Đỗ]

Hello Alvaro

Sorry for a late reply. I just found out many emails were sent to my spam
box, including yours.
The new sql code that you sent me works well. Thanks for your help.
Best regards
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 2, 8 thg 6, 2020 vào lúc 01:43 Alvaro Cornejo <
cornejo.alv...@gmail.com> đã viết:

> Hi Quỳnh,
>
> There were a couple of errors in your query.
>
> Try this:
>
> -
> SELECT b.biblionumber, SUBSTRING_INDEX(m.isbn, ' ', 1) AS isbn, b.title
>
> FROM items i
>
> LEFT JOIN biblioitems m USING (biblioitemnumber)
>
> LEFT JOIN biblio b ON (i.biblionumber=b.biblionumber)
>
> WHERE DATE_SUB(CURDATE(),INTERVAL 180 DAY) <= i.dateaccessioned AND m.isbn
> IS NOT NULL AND m.isbn != ""
>
> ORDER BY rand()
>
> LIMIT 7
> --
>
> I´ve tried in my system (19.11) system and it works now.
>
> Regards
>
> Alvaro
>
>
>
> ||
>  Stay safe / Cuídate/  Reste sécurisé
> *7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
> mesure.
>  *q *Recycle always / Recicla siempre / Recyclez toujours
>  P Print only if absolutely necessary / Imprime solo si es necesario /
> Imprimez seulement si nécessaire
>
>
>
>
>
> Le sam. 6 juin 2020 à 20:51, Quỳnh Vũ Đỗ  a
> écrit :
>
>> Hello everyone,
>> I am using a test database of our Library on Koha 19.11.06 (just
>> auto-upgraded from 19.11.05) on Ubuntu 16.04.6 LTS.
>> In the process of customizing the OPAC and installing the COverflow plugin
>> as described at:
>> https://bywatersolutions.com/education/coverflow-blog-post-update
>> I have created the sql report by copying and paste the described content
>> on
>> that page:
>>
>> Report SQL:
>>
>> SELECT b.biblionumber, SUBSTRING_INDEX(m.isbn, ‘ ‘, 1) AS isbn, b.title
>>
>> FROM items i
>>
>> LEFT JOIN biblioitems m USING (biblioitemnumber)
>>
>> LEFT JOIN biblio b ON (i.biblionumber=b.biblionumber)
>>
>> WHERE DATE_SUB(CURDATE(),INTERVAL 180 DAY) <= i.dateaccessioned AND
>> m.isbn IS NOT NULL AND m.isbn != ”
>>
>> ORDER BY rand()
>>
>> LIMIT 7
>>
>>
>> The only modification I have brought to the original code was to change
>> the
>> INTERVAL from 30 DAY to 180 DAY as the last operation made on that
>> database
>> was made on 25th February 2020.
>> On running the report I got the following error message:
>> "The database returned the following error:
>> Incorrect parameters in the call to native function 'substring_index'
>> Please check the log for further details"
>>
>> So I checked the log at /var/log/koha/library/intranet-error.log which
>> indicated:
>>
>> [Sun Jun 07 08:21:27.385286 2020] [cgi:error] [pid 30474] [client
>> 127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
>> \r:
>> /usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
>> http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
>> [Sun Jun 07 08:21:27.385426 2020] [cgi:error] [pid 30474] [client
>> 127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
>> LIMIT ?, ?" with ParamValues: 0=0, 1=7] at
>> /usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl line 1001.:
>> /usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
>> http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
>> [Sun Jun 07 08:21:27.385605 2020] [cgi:error] [pid 30474] [client
>> 127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
>> DBD::mysql::st fetchrow_arrayref failed: fetch() without execute() [for
>> Statement "SELECT b.biblionumber, SUBSTRING_INDEX(m.isbn, \xe2\x80\x98
>> \xe2\x80\x98, 1) AS isbn, b.title\r:
>> /usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
>> http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
>> [Sun Jun 07 08:21:27.385660 2020] [cgi:error] [pid 30474] [client
>> 127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
>> FROM items i\r: /usr/share/koha/intranet/cgi-bin/reports/
>> guided_reports.pl,
>> referer: http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
>> [Sun Jun 07 08:21:27.385745 2020] [cgi:error] [pid 30474] [cli

Re: [Koha] Editing koha-sites.conf to allow for multiple instances

[Quỳnh Vũ Đỗ]

Hello,
I think that you should attribute two different ports to your intranet
(Staff login) and your OPAC. Something like:

> INTRAPORT="8000"
> INTRAPREFIX=""
> INTRASUFFIX="-admin"
> OPACPORT="80"
> OPACPREFIX="opac"
> OPACSUFFIX=""
In this situation the port "80" is the default one for the web server
Apache to 'listen" and will display the OPAC interface (if it is public).
To log in the intranet (Staff login) to administer Koha and the library
database, then you would need to add ":8000" to the end of your URL like "
https://your_domain:8000/;.

In the case of two Koha instances running on the same server. I think that
you would have a koha-conf.xml for each instance (under
/etc/koha/sites/instance_name/) and you should have, in my opinion, two
different sets of ports like ports 8000 and 8080 for one instance and ports
9000 and 9090 for the second instance. The port numbers I would choose are
such that you can remember which instance you want to access on the server,
and then which one is the OPAC and which one is for staff login.

You would also need to indicate the ports to which the (Apache) web server
should be listening in the file /etc/apache2/ports.conf, which for the
example above would be inserting the following lines in that file:

LISTEN 8000
LISTEN 8080
LISTEN 9000
LISTEN 9090

As I'm not a specialist, especially for running two instances of Koha, I
hope other contributors will correct me if I've been wrong somewhere.
Best regards
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 4, 24 thg 6, 2020 vào lúc 03:13 Sterling Jenson <
sterlingjen...@gmail.com> đã viết:

> Greetings all,
>
> I am experimenting with setting up a second instance of Koha on my server.
> While I have the second one up running, including SSL, I cannot figure out
> how to edit the koha-sites.conf file so that I can access the staff page
> using https://[library1]-admin.[domain].org and
> https://[library2]-admin.[domain].org
> instead of https://www.[domain].org:[portnumber].  I have already tried to
> copy and paste this block:
>
> DOMAIN="[domain]"
> > INTRAPORT="80"
> > INTRAPREFIX=""
> > INTRASUFFIX="-admin"
> > OPACPORT="80"
> > OPACPREFIX="opac"
> > OPACSUFFIX=""
> >
>
> and change the ports that were used, but, alas, no luck.  Thoughts on what
> step I am missing?  Or did I overlook the information in the Wiki?  Thanks
> in advance.
>
> Best,
>
> Sterling
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] [Koha-devel] Koha 20.05.00 Released

[Quỳnh Vũ Đỗ]

hello Jonathan
Installing that package did the trick. Now  "About Koha" works!
Thanks for the help and best regards
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 2, 15 thg 6, 2020 vào lúc 14:56 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> đã viết:

> Hello Quynh,
>
> Try to install libcpan-meta-requirements-perl as well (this should
> only be done on Ubuntu 16.04).
>
> Regards,
> Jonathan
>
> Le lun. 15 juin 2020 à 03:57, Quỳnh Vũ Đỗ  a
> écrit :
> >
> > Hello Jonathan
> >
> > I was using Koha 19.11.06 on Ubuntu 16.04.6 LTS. After doing an upgrade,
> Koha upgraded to 20.05.00 Alpha release.
> > After logging in the staff client and going to "About Koha", I got the
> following  error:
> >
> > Software error:
> >
> > Can't locate object method "structured_requirements_for_module" via
> package "CPAN::Meta::Requirements" at
> /usr/share/koha/lib/C4/Installer/PerlModules.pm line 66.
> >
> > For help, please send mail to the webmaster ([no address given]), giving
> this error message and the time and date of the error.
> >
> > So I did the following in a terminal, as recommanded:
> > koha@kohaServer:~$ sudo apt install libcpan-meta-perl
> > [sudo] password for koha:
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > libcpan-meta-perl is already the newest version (2.150010-1).
> > The following packages were automatically installed and are no longer
> required:
> >   libpdf-api2-simple-perl snapd-login-service tinymce
> > Use 'sudo apt autoremove' to remove them.
> > 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> > koha@kohaServer:~$
> >
> > Thus there might be another problem elsewhere.
> >
> > Of course, I should upgrade Ubuntu to 18.04 which I eventually will do
> but I met other problems with fresh install of Ubuntu 18.04.4 LTS because
> when installing koha-common I got 2 dependencies problems flagged as not
> resolvable and, thus was not able to install koha. I met that problem twice
> on installation to 2 different computers.
> >
> > Best regards
> > Quynh
> > =
> > M. Vũ Đỗ Quỳnh (Ph.D)
> > Trường Đại học Thăng Long - Université de Thang Long - Thang Long
> University (Hanoi, Vietnam)
> > Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la
> coopération internationale - Vice-Rector in charge of International
> Cooperation
> > Web: http://thanglong.edu.vn/
> >
> >
> > Vào Th 3, 9 thg 6, 2020 vào lúc 19:35 Jonathan Druart <
> jonathan.dru...@bugs.koha-community.org> đã viết:
> >>
> >> Hi everybody,
> >>
> >> IMPORTANTE NOTE
> >>
> >> If you want to upgrade to 20.05.00 you should know that we have 2
> >> major bugs that you may hit.
> >>
> >> 1. There was a change in 20.05. Before we silently ignored wrong
> >> permissions, now we force the logging system to be setup correctly
> >> (bug 25172)
> >> You must give permission to your koha user by changing the owner of
> >> the Koha log directory:
> >>   $ chown -R USER:USER /var/log/koha/INSTANCE
> >> This one will be addressed in the next release.
> >>
> >> 2. If you are upgrading with an OS that is not supported (like Ubuntu
> >> 16.04) you may see:
> >>
> >> Can't locate object method "structured_requirements_for_module" via
> >> package "CPAN::Meta::Requirements" at
> >> /usr/share/koha/lib/C4/Installer/PerlModules.pm line 66.
> >> or
> >> Can't locate object method "phases" via package "CPAN::Meta::Prereqs"
> >> at /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55
> >>
> >> => libcpan-meta-perl must be version 2.150010. If not you can try
> >> `sudo apt install libcpan-meta-perl`. Better would be to upgrade the
> >> system of course.
> >>
> >> Regards,
> >> Jonathan
> >>
> >>
> >> Le dim. 31 mai 2020 à 23:31, Renvoize, Martin
> >>  a écrit :
> >> >
> >> > Hello Everyone,
> >> >
> >> > It is with great pleasure I am able to announce the release of Koha
> 20.05, a major release of 

Re: [Koha] [Koha-devel] Koha 20.05.00 Released

[Quỳnh Vũ Đỗ]

Hello Jonathan

I was using Koha 19.11.06 on Ubuntu 16.04.6 LTS. After doing an upgrade,
Koha upgraded to 20.05.00 Alpha release.
After logging in the staff client and going to "About Koha", I got the
following  error:
Software error:

Can't locate object method "structured_requirements_for_module" via
package "CPAN::Meta::Requirements" at
/usr/share/koha/lib/C4/Installer/PerlModules.pm line 66.

For help, please send mail to the webmaster ([no address given]), giving
this error message and the time and date of the error.
So I did the following in a terminal, as recommanded:
koha@kohaServer:~$ sudo apt install libcpan-meta-perl
[sudo] password for koha:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libcpan-meta-perl is already the newest version (2.150010-1).
The following packages were automatically installed and are no longer
required:
  libpdf-api2-simple-perl snapd-login-service tinymce
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
koha@kohaServer:~$

Thus there might be another problem elsewhere.

Of course, I should upgrade Ubuntu to 18.04 which I eventually will do but
I met other problems with fresh install of Ubuntu 18.04.4 LTS because when
installing koha-common I got 2 dependencies problems flagged as not
resolvable and, thus was not able to install koha. I met that problem twice
on installation to 2 different computers.

Best regards
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 3, 9 thg 6, 2020 vào lúc 19:35 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> đã viết:

> Hi everybody,
>
> IMPORTANTE NOTE
>
> If you want to upgrade to 20.05.00 you should know that we have 2
> major bugs that you may hit.
>
> 1. There was a change in 20.05. Before we silently ignored wrong
> permissions, now we force the logging system to be setup correctly
> (bug 25172)
> You must give permission to your koha user by changing the owner of
> the Koha log directory:
>   $ chown -R USER:USER /var/log/koha/INSTANCE
> This one will be addressed in the next release.
>
> 2. If you are upgrading with an OS that is not supported (like Ubuntu
> 16.04) you may see:
>
> Can't locate object method "structured_requirements_for_module" via
> package "CPAN::Meta::Requirements" at
> /usr/share/koha/lib/C4/Installer/PerlModules.pm line 66.
> or
> Can't locate object method "phases" via package "CPAN::Meta::Prereqs"
> at /home/vagrant/kohaclone/C4/Installer/PerlModules.pm line 55
>
> => libcpan-meta-perl must be version 2.150010. If not you can try
> `sudo apt install libcpan-meta-perl`. Better would be to upgrade the
> system of course.
>
> Regards,
> Jonathan
>
>
> Le dim. 31 mai 2020 à 23:31, Renvoize, Martin
>  a écrit :
> >
> > Hello Everyone,
> >
> > It is with great pleasure I am able to announce the release of Koha
> 20.05, a major release of the Koha open source integrated library system.
> >
> > This release includes 13 new features, 275 enhancements, 592 bugfixes.
> Please see the release notes for further details:
> https://koha-community.org/koha-20-05-released/
> >
> > It is the work of many librarians, developers and community members who
> have donated a huge number of hours to keep the project moving forward. My
> thanks go out to all who contributed.
> >
> > This is my final release as a release manager and I'd like to extend my
> personal thanks to a fantastic team.
> >
> > Special thanks go out to Mason James,  Tomas Cohen and Jonathan Druart,
> all who stepped in during the final weeks of the cycle to ensure the
> packaging would work as expected for Debian 10 as well as finding and
> fixing bugs right up to the very end of the cycle.  I cannot overstate what
> a great team I've had behind me this cycle and I feel we have achieved a
> huge amount.
> >
> > Debian packages, will be available on the standard community
> repositories soon having been tested via our beta channels for the past two
> weeks.
> >
> > Many thanks,
> >
> > Martin Renvoize
> >
> > Development Team Manager
> >
> > Community Release Manager (19.11, 20.05)
> >
> >
> >
> > Phone: +44 (0) 1483 378728
> >
> > Mobile: +44 (0) 7725 985 636
> >
> > Email: martin.renvo...@ptfs-europe.com
> >
> > Fax: +44 (0) 800 756 6384
> >
> >
> > www.ptfs-europe.com
> >
> >
> >
> >
> >
> >
> >
> > Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30
> >
> >
> > The information contained in this email message may be privileged,
> confidential and protected from disclosure. If you are not the intended
> recipient, any dissemination, distribution or copying is strictly
> prohibited. If you think that you have received this email message in
> error, please 

[Koha] Coverflow installation problems

[Quỳnh Vũ Đỗ]

Hello everyone,
I am using a test database of our Library on Koha 19.11.06 (just
auto-upgraded from 19.11.05) on Ubuntu 16.04.6 LTS.
In the process of customizing the OPAC and installing the COverflow plugin
as described at:
https://bywatersolutions.com/education/coverflow-blog-post-update
I have created the sql report by copying and paste the described content on
that page:

Report SQL:

SELECT b.biblionumber, SUBSTRING_INDEX(m.isbn, ‘ ‘, 1) AS isbn, b.title

FROM items i

LEFT JOIN biblioitems m USING (biblioitemnumber)

LEFT JOIN biblio b ON (i.biblionumber=b.biblionumber)

WHERE DATE_SUB(CURDATE(),INTERVAL 180 DAY) <= i.dateaccessioned AND
m.isbn IS NOT NULL AND m.isbn != ”

ORDER BY rand()

LIMIT 7


The only modification I have brought to the original code was to change the
INTERVAL from 30 DAY to 180 DAY as the last operation made on that database
was made on 25th February 2020.
On running the report I got the following error message:
"The database returned the following error:
Incorrect parameters in the call to native function 'substring_index'
Please check the log for further details"

So I checked the log at /var/log/koha/library/intranet-error.log which
indicated:

[Sun Jun 07 08:21:27.385286 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl: \r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385426 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
LIMIT ?, ?" with ParamValues: 0=0, 1=7] at
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl line 1001.:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385605 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
DBD::mysql::st fetchrow_arrayref failed: fetch() without execute() [for
Statement "SELECT b.biblionumber, SUBSTRING_INDEX(m.isbn, \xe2\x80\x98
\xe2\x80\x98, 1) AS isbn, b.title\r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385660 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
FROM items i\r: /usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl,
referer: http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385745 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
LEFT JOIN biblioitems m USING (biblioitemnumber)\r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385834 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
LEFT JOIN biblio b ON (i.biblionumber=b.biblionumber)\r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.385966 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
WHERE DATE_SUB(CURDATE(),INTERVAL 180 DAY) <= i.dateaccessioned AND m.isbn
IS NOT NULL AND m.isbn != \xe2\x80\x9d\r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.386024 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
ORDER BY rand()\r: /usr/share/koha/intranet/cgi-bin/reports/
guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.386072 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl: \r:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl
[Sun Jun 07 08:21:27.386321 2020] [cgi:error] [pid 30474] [client
127.0.0.1:39572] AH01215: [Sun Jun  7 08:21:27 2020] guided_reports.pl:
LIMIT ?, ?" with ParamValues: 0=0, 1=7] at
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl line 839.:
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl, referer:
http://localhost:8080/cgi-bin/koha/reports/guided_reports.pl

As I have limited knowledge in SQL coding, I am unsure of what to do (I
remember to have tested that SQL code with Koha 16.05 and it worked then).

Does anyone have met that problem and possibly have a hint for resolution?
Thanks
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération

Re: [Koha] Reset the password for superlibrarian ?

[Quỳnh Vũ Đỗ]

Hello Jonathan

Thanks for the info. I already solved my problem but I will try it as it's
good to know.
Best regards
Quynh


=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 2, 18 thg 5, 2020 vào lúc 15:46 Jonathan Druart <
jonathan.dru...@bugs.koha-community.org> đã viết:

> Hello Quynh,
>
> Use the script misc/admin/set_password.pl
>
> Regards,
> Jonathan
>
> Le sam. 16 mai 2020 à 09:47, Quỳnh Vũ Đỗ  a
> écrit :
> >
> > Hello everyone,
> > Thanks to useful advice provided by the list community, I was able to
> > upgrade from Koha 3.18 to Koha 19.11.05
> >
> > I could open the Staff login window. I am now faced with login in to Koha
> > as administrator to perform some maintenance tasks. I managed to found
> how
> > to get into a Koha shell and run the script
> > /usr/share/koha/bin/devel/create_superlibrarian.pl
> > With Usage:
> > create_superlibrarian.pl --userid  --password 
> > --branchcode  --categorycode  --cardnumber
> > 
> > So I tried with values without any quotes, with double quotes  and simple
> > quotes to always face the same error:
> >
> > DBD::mysql::st execute failed: Duplicate entry 'BGH01' for key
> > 'cardnumber' [for Statement "INSERT INTO `borrowers` ( `borrowernumber`,
> > `branchcode`, `cardnumber`, `categorycode`, `dateenrolled`, `dateexpiry`,
> > `flags`, `password`, `privacy`, `surname`, `userid`) VALUES ( ?, ?, ?, ?,
> > ?, ?, ?, ?, ?, ?, ? )" with ParamValues: 0=undef, 1='TLU', 2='BGH01',
> > 3='CB', 4='2020-05-16T14:29:34', 5='2021-05-16T14:29:34', 6='1', 7='!',
> > 8=1, 9=undef, 10="2"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line
> > 1834.
> >
> > But as the superlibraian already exists, then I cannot insert an other
> one
> > - so the duplicate entry. What I would need is a simple UPDATE statement
> to
> > reset the password of the superlibrarian with userid thanglong with a
> > "newpassword"
> >
> > Is it safe to enter the following command from a mysql shell
> > USE koha_library;
> > UPDATE `borrowers` SET `password` = PASSWORD("newpassord") WHERE
> > `userid`="thanglong";
> >
> > I eventually tried it, but still was not able to log in.
> > Any hint on how to reset that password for the first row of the table
> > boowers?
> > Thanks for reading
> > Quynh
> >
> > =
> > M. Vũ Đỗ Quỳnh (Ph.D)
> > Trường Đại học Thăng Long - Université de Thang Long - Thang Long
> > University (Hanoi, Vietnam)
> > Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la
> coopération
> > internationale - Vice-Rector in charge of International Cooperation
> > Web: http://thanglong.edu.vn/
> > ___
> >
> > Koha mailing list  http://koha-community.org
> > Koha@lists.katipo.co.nz
> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hello Katrin

Thanks for the info.

Indeed I was able to solve the staff login problem because in the borrowers
table there was a duplicate in the field 'userid' which should not have
been. I edited the duplicate userid (same student but with a different
student card number). There were also problems with the old field 'privacy'
as 128 rows had a value of '2' instead of either '0' or '1'. I did an
update sql query to put all those '2' values to '1' and after that
upgrading was OK.

Instead of using the web interface to do the database upgrade, I followed
the advice of (sorry, I forgot the name) of running the upgrade in a
terminal (koha-upgrade-schema library) which pointed at the two problems
met above.

The problem of searching the OPAC (an other post I made) after the upgrade
was solved by running in a terminal 'koha-rebuild-zebra -v -f library),
which is something that should be done after each upgrade from an older
database to a newer version of Koha.

Best regards
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 2, 18 thg 5, 2020 vào lúc 04:31 Katrin Fischer <
katrin.fischer...@web.de> đã viết:

> Hi,
>
> misc/batchRebuildBiblioTables.pl has to be run from command line, there
> is no option to make this change from the GUI.
>
> The database user and the superlibrarian accounts are separate things.
> If you don't remember the password for the superlibrarian, you can
> create another with a different userid/cardnumber and use that to get
> back into the system.
>
> Then you can also use it to reset the password on your old
> superlibrarian account or to delete it.
>
> Hope that helps,
>
> Katrin
>
> On 16.05.20 10:19, Quỳnh Vũ Đỗ wrote:
> > Hi Jason
> >   I did it as you instructed to note all the information output to the
> > terminal.
> > I was able to fix the main errors (two actually) and at the second run,
> all
> > went rather smoothly and I could display the login window.
> > Still some issues to be fixed through library maintenance with some perl
> > scripts, which I believe might be the source of the OPAC still not
> > returning search results on the catalog.
> > For example I had messages like this one:
> > Upgrade to 19.06.00.018 done (Bug 11529: Add medium, subtitle and part
> > information to biblio table)
> > NOTE: misc/batchRebuildBiblioTables.pl should be run to populate the
> fields
> > introduced in bug 11529. It may take some time for larger databases.
> >
> > I understand that either I should be able to log in as staff
> administrator
> > to perform that task OR get into a koha shell to run that script. Is that
> > correct?
> >
> > I am now trying to find how to reset the superlibrarian password to be
> able
> > to log in to perform that maintenance.
> >
> ___
>
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hi
I managed to solve all the problems.
After studying the outputs of running in a terminal koha-upgrade schema and
editing accordingly the dump sql file of the library, the upgrade from 3.18
to 19.11. was successful.

I solved the OPAC search results returning nothing by running in a terminal
"koha-rebuild-zebra -v -f library" as found in documentation found on the
internet. After that everything looks "normal". The people of our library
still have to tell me everything's right. Works now has to be done on the
OPAC customization.

Again, thanks for all the useful information I gained from this list and
its members.
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 7, 16 thg 5, 2020 vào lúc 15:19 Quỳnh Vũ Đỗ <
quyn...@thanglong.edu.vn> đã viết:

> Hi Jason
>  I did it as you instructed to note all the information output to the
> terminal.
> I was able to fix the main errors (two actually) and at the second run,
> all went rather smoothly and I could display the login window.
> Still some issues to be fixed through library maintenance with some perl
> scripts, which I believe might be the source of the OPAC still not
> returning search results on the catalog.
> For example I had messages like this one:
> Upgrade to 19.06.00.018 done (Bug 11529: Add medium, subtitle and part
> information to biblio table)
> NOTE: misc/batchRebuildBiblioTables.pl should be run to populate the
> fields introduced in bug 11529. It may take some time for larger databases.
>
> I understand that either I should be able to log in as staff administrator
> to perform that task OR get into a koha shell to run that script. Is that
> correct?
>
> I am now trying to find how to reset the superlibrarian password to be
> able to log in to perform that maintenance.
>
> Quynh
> =
> M. Vũ Đỗ Quỳnh (Ph.D)
> Trường Đại học Thăng Long - Université de Thang Long - Thang Long
> University (Hanoi, Vietnam)
> Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
> internationale - Vice-Rector in charge of International Cooperation
> Web: http://thanglong.edu.vn/
>
>
> Vào Th 6, 15 thg 5, 2020 vào lúc 23:57 Jason Boyer <
> jbo...@equinoxinitiative.org> đã viết:
>
>> Replies inline below
>>
>> On May 15, 2020, at 12:48 PM, Quỳnh Vũ Đỗ 
>> wrote:
>>
>> Hi,
>>
>>
>> Vào Th 6, 15 thg 5, 2020 vào lúc 22:25 Jason Boyer <
>> jbo...@equinoxinitiative.org> đã viết:
>>
>>> Hi, this sounds similar to a problem I ran into recently upgrading a
>>> 3.20 database to 19.11. You’ll probably have to do the drop/re-import
>>> procedure at least 2 more times to fix this, but doing this should help:
>>>
>>> By this I understand I should try to do incremental drop/re-import, i.e.
>> once one drop-reimport cycle is successful, I would mysqldump the
>> "upgraded" 19.11 database containing the 3.18 values and then drop again
>> the database to reload it with the new dump of the 19.11. Is this
>> interpretation of mine correct?
>>
>>
>> Not quite. Because an error early on can cause additional failures later,
>> the process I’m referring to is this:
>> 1. Load the 3.18 database
>> 2. Try to upgrade it to 19.11, and save all of the output
>> 3. Drop the 19.11 database
>> 4. Load the 3.18 database again
>> 5. Fix the issues from the 19.11 upgrade output
>> 6. Try to upgrade to 19.11 again, saving the output again just in case
>> 7. If there are additional errors at this point, make note of them, then
>> go to step 4 and try again, fixing the old issues and these new ones.
>>
>> When you are able to load the 3.18 database, make a few specific data /
>> constraint changes, run the schema upgrade with no errors, then you’re done
>> and your database will be in good shape. (This is a great time for a fresh
>> backup :-) )
>>
>>
>>
>>> Instead of using the web interface, after re-importing the 3.18 database
>>> use koha-upgrade-schema  at a terminal and capture the output
>>> in whatever way is convenient to refer to later. At some point there will
>>> most likely be some kind of error that will cause an update to fail, though
>>> the upgrade script will continue on. In my case it was an invalid default
>>> value for the created_on timestamp (-00-00 :00) on the
>>> virtualshelves table

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hi Jason
 I did it as you instructed to note all the information output to the
terminal.
I was able to fix the main errors (two actually) and at the second run, all
went rather smoothly and I could display the login window.
Still some issues to be fixed through library maintenance with some perl
scripts, which I believe might be the source of the OPAC still not
returning search results on the catalog.
For example I had messages like this one:
Upgrade to 19.06.00.018 done (Bug 11529: Add medium, subtitle and part
information to biblio table)
NOTE: misc/batchRebuildBiblioTables.pl should be run to populate the fields
introduced in bug 11529. It may take some time for larger databases.

I understand that either I should be able to log in as staff administrator
to perform that task OR get into a koha shell to run that script. Is that
correct?

I am now trying to find how to reset the superlibrarian password to be able
to log in to perform that maintenance.

Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/


Vào Th 6, 15 thg 5, 2020 vào lúc 23:57 Jason Boyer <
jbo...@equinoxinitiative.org> đã viết:

> Replies inline below
>
> On May 15, 2020, at 12:48 PM, Quỳnh Vũ Đỗ 
> wrote:
>
> Hi,
>
>
> Vào Th 6, 15 thg 5, 2020 vào lúc 22:25 Jason Boyer <
> jbo...@equinoxinitiative.org> đã viết:
>
>> Hi, this sounds similar to a problem I ran into recently upgrading a 3.20
>> database to 19.11. You’ll probably have to do the drop/re-import procedure
>> at least 2 more times to fix this, but doing this should help:
>>
>> By this I understand I should try to do incremental drop/re-import, i.e.
> once one drop-reimport cycle is successful, I would mysqldump the
> "upgraded" 19.11 database containing the 3.18 values and then drop again
> the database to reload it with the new dump of the 19.11. Is this
> interpretation of mine correct?
>
>
> Not quite. Because an error early on can cause additional failures later,
> the process I’m referring to is this:
> 1. Load the 3.18 database
> 2. Try to upgrade it to 19.11, and save all of the output
> 3. Drop the 19.11 database
> 4. Load the 3.18 database again
> 5. Fix the issues from the 19.11 upgrade output
> 6. Try to upgrade to 19.11 again, saving the output again just in case
> 7. If there are additional errors at this point, make note of them, then
> go to step 4 and try again, fixing the old issues and these new ones.
>
> When you are able to load the 3.18 database, make a few specific data /
> constraint changes, run the schema upgrade with no errors, then you’re done
> and your database will be in good shape. (This is a great time for a fresh
> backup :-) )
>
>
>
>> Instead of using the web interface, after re-importing the 3.18 database
>> use koha-upgrade-schema  at a terminal and capture the output
>> in whatever way is convenient to refer to later. At some point there will
>> most likely be some kind of error that will cause an update to fail, though
>> the upgrade script will continue on. In my case it was an invalid default
>> value for the created_on timestamp (-00-00 :00) on the
>> virtualshelves table, but it could be any number of things depending on
>> past/present mysql versions and data consistency.
>>
>> Collect all of the errors in the koha-upgrade-schema output and find out
>> how to address them, then re-import the 3.18 db once more and fix them
>> before running koha-upgrade-schema. If you need help solving the problems I
>> believe the output of koha-upgrade-schema is safe to post publicly if you’d
>> like to attach a text file or share a link to a paste with the list (but
>> you may want to double-check before doing so).
>>
>>
> Do you think that it would be safe enough to fix values leading to fault
> by doing phpmyadmin edition directly in tables ? like replacing value
> "-00-00" by "NULL" for instance?
>
> Quynh
>
>
> If you’re more comfortable with phpmyadmin that should be fine. The most
> important thing is to make all of the required changes before starting the
> schema upgrade.
>
> Jason
>
> --
> Jason Boyer
> Senior System Administrator
> Equinox Open Library Initiative
> phone:  +1 (877) Open-ILS (673-6457)
> email:  jbo...@equinoxinitiative.org 
> web:  https://EquinoxInitiative.org/
>
>
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Reset the password for superlibrarian ?

[Quỳnh Vũ Đỗ]

Hello everyone,
Thanks to useful advice provided by the list community, I was able to
upgrade from Koha 3.18 to Koha 19.11.05

I could open the Staff login window. I am now faced with login in to Koha
as administrator to perform some maintenance tasks. I managed to found how
to get into a Koha shell and run the script
/usr/share/koha/bin/devel/create_superlibrarian.pl
With Usage:
create_superlibrarian.pl --userid  --password 
--branchcode  --categorycode  --cardnumber

So I tried with values without any quotes, with double quotes  and simple
quotes to always face the same error:

DBD::mysql::st execute failed: Duplicate entry 'BGH01' for key
'cardnumber' [for Statement "INSERT INTO `borrowers` ( `borrowernumber`,
`branchcode`, `cardnumber`, `categorycode`, `dateenrolled`, `dateexpiry`,
`flags`, `password`, `privacy`, `surname`, `userid`) VALUES ( ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ? )" with ParamValues: 0=undef, 1='TLU', 2='BGH01',
3='CB', 4='2020-05-16T14:29:34', 5='2021-05-16T14:29:34', 6='1', 7='!',
8=1, 9=undef, 10="2"] at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line
1834.

But as the superlibraian already exists, then I cannot insert an other one
- so the duplicate entry. What I would need is a simple UPDATE statement to
reset the password of the superlibrarian with userid thanglong with a
"newpassword"

Is it safe to enter the following command from a mysql shell
USE koha_library;
UPDATE `borrowers` SET `password` = PASSWORD("newpassord") WHERE
`userid`="thanglong";

I eventually tried it, but still was not able to log in.
Any hint on how to reset that password for the first row of the table
boowers?
Thanks for reading
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Opac not searchable after upgrading database from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hello everyone

After upgrading a Koha database from version 3.18 to 19.11, I was not able
to log in in the staff/administration of Koha as I obtained a "Software
Error" message. However, I was able to get to the OPAC page (at
http://localhost:8000/) but any search returned nothing.
I checked with Phpmyadmin that the biblio table of koha_library was
effectively filled with the data of the 3.18 database (which it was), but
the search of strings that were present returned nothing.

Does someone have encountered that problem and knows the solution?
I am thinking of running in a terminal the command "koha-rebuild-zebra" but
I prefer to listen to some sound advice first.

Thanks for reading
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hi,


Vào Th 6, 15 thg 5, 2020 vào lúc 22:25 Jason Boyer <
jbo...@equinoxinitiative.org> đã viết:

> Hi, this sounds similar to a problem I ran into recently upgrading a 3.20
> database to 19.11. You’ll probably have to do the drop/re-import procedure
> at least 2 more times to fix this, but doing this should help:
>
> By this I understand I should try to do incremental drop/re-import, i.e.
once one drop-reimport cycle is successful, I would mysqldump the
"upgraded" 19.11 database containing the 3.18 values and then drop again
the database to reload it with the new dump of the 19.11. Is this
interpretation of mine correct?



> Instead of using the web interface, after re-importing the 3.18 database
> use koha-upgrade-schema  at a terminal and capture the output
> in whatever way is convenient to refer to later. At some point there will
> most likely be some kind of error that will cause an update to fail, though
> the upgrade script will continue on. In my case it was an invalid default
> value for the created_on timestamp (-00-00 :00) on the
> virtualshelves table, but it could be any number of things depending on
> past/present mysql versions and data consistency.
>
> Collect all of the errors in the koha-upgrade-schema output and find out
> how to address them, then re-import the 3.18 db once more and fix them
> before running koha-upgrade-schema. If you need help solving the problems I
> believe the output of koha-upgrade-schema is safe to post publicly if you’d
> like to attach a text file or share a link to a paste with the list (but
> you may want to double-check before doing so).
>
>
Do you think that it would be safe enough to fix values leading to fault by
doing phpmyadmin edition directly in tables ? like replacing value
"-00-00" by "NULL" for instance?

Quynh
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Staff login problems after upgrading from Koha 3.18 to 19.11

[Quỳnh Vũ Đỗ]

Hello everyone,
Our library has been using a Vietnamized version of Koha 3.18 since mid
2014, running on Ubuntu server 14.04 LTS. No upgrade of the system has been
made since and the server had a hardware problem (mainboard) last February.
In an attempt to restore the Koha 3.18 database (a dump sql file of 1.8
Gb), I installed Koha 19.11 on an Ubuntu 16.04.6 LTS Desktop with a LAMP
stack.

After consulting with the mailing list yesterday, I followed the steps that
were indicated, i.e Drop the 19.11 koha_library database, recreate it empty
and then import the Koha 3.18 database sql dump file.
Then I went to the staff login page http://localhost:8080 where I was
welcomed by the login window for the web installation. I followed all the
steps with success although at the crucial one (starting upgrading from
3.18 to 19.11) I had a Server timeout after 10-15 minutes waiting. I
repeated the start upgrade procedure and was met again with a server
Timeout. Then I had to go to work.

At my office, I used the Easykoha Live DVD to install Koha 16.05 along with
Ubuntu 14.04 LTS on an experimental partition. I then followed the same
procedure as described a bove to do an upgrade of our Koha 3.18 database
towards Koha 16.05. This, because the structure between the two database
versions did not seem too differ too much (only two more tables in the
16.05 version). The upgrade from 3.18 to 16.05 was not successful though
and I had a full web page filled with the errors that were met.

When I came back home, I had the nice surprise to see that the upgrade from
3.18 to 19.11 had succeeded as I was welcomed by this message: "Updating
database structure: Everything went OK. Update Done" and a blue button
telling "Continue to log in to Koha". After clicking the button, I had a
display of "Software error" that said:

DBIx::Class::Storage::DBI::_dbh_execute(): Unknown column 'me.anonymized'
in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 93

The line 93 (in bold below) is part of a subroutine as follows:

sub find {
my ( $self, @pars ) = @_;

my $object;

unless (!@pars || none { defined($_) } @pars) {
*my $result = $self->_resultset()->find(@pars);*
if ($result) {
$object = $self->object_class()->_new_from_dbic($result);
}
}

return $object;
}

Any hints on how to solve this problem would be greatly appreciated.


Thanks for your attention and help.
Quynh

=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Migrating Koha database from version 3.18 to 19.11?

[Quỳnh Vũ Đỗ]

Hello everyone

Our library has been using a Vietnamized version of Koha 3.18 since mid
2014, running on Ubuntu server 14.04 LTS. No upgrade of the system has been
made since and the server had a hardware problem (mainboard) last February.

We have a mysqldump of the Koha database (size about 1,8 GB).

So what we are trying to do is to install the latest Koha version (19.11)
on a fresh Ubuntu 16.04.6 LTS (Desktop) and then to replenish the empty
Koha tables through SQL inserts in the tables using sql exports of the
related fields from the old database. For that we have been comparing the
structure of the tables of Koha 3.18 and 19.11 with the tool provided at
http://schema.koha-community.org/

Can this way of proceeding, although tedious it might be, be successful or
not ?
If not, could someone have suggestions ?
Thanks for your attention.
Quynh
=
M. Vũ Đỗ Quỳnh (Ph.D)
Trường Đại học Thăng Long - Université de Thang Long - Thang Long
University (Hanoi, Vietnam)
Phó Hiệu Trưởng, phụ trách HTQT - Vice-recteur chargé de la coopération
internationale - Vice-Rector in charge of International Cooperation
Web: http://thanglong.edu.vn/
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha