https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19546

--- Comment #8 from Tomás Cohen Arazi <tomasco...@gmail.com> ---
(In reply to Galen Charlton from comment #7)
> Reopening. Saw this happen on a Debian 8.10 system with a fresh install of
> 17.11.02 from package.
> 
> A (truly terrible workaround) got Plack running:
> 
> /usr/share/perl5/Mojolicious/Plugin && ln -s /usr/share/koha/lib/Koha Koha
> 
> Version of Mojolicious is 7.21 from the 7.21+dfsg-1~kohadev1 package.

I don't manage to reproduce it.

I have installed 17.11.02-1 (17.11 repo) on a clean box:

   $ vagrant init debian/jessie64

only added port mappings to be able to access Koha (in Vagrantfile):
config.vm.network :forwarded_port, guest: 80,   host: 8080, auto_correct: true 
# OPAC
config.vm.network :forwarded_port, guest: 8080, host: 8081, auto_correct: true 
# INTRA

I then added 8080 to /etc/apache2/ports.conf and tweaked
/etc/apache2/sites-enabled/kohadev.conf so intranet uses port 8080.

Once I populate the DB I manage to access the API (with and without Plack
enabled). The only problem I noticed is that the rewrite bits for the API (in
apache) are not working, so I needed to use /api/v1/app.pl/api/v1/patrons to
access the API when Plack is disabled.

If you still have the VM in which you see the failure, could you try using a +
sufix in the V1.pm line that includes the pagination plugin ? I'm not sure
right now what was the way to avoid Mojolicious prefixing hte plugin name.

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to