Please open a new bug report. I will not be able to provide a patch, I
still cannot recreate.
On Thu, 26 Jan 2017 at 07:57 clint.deckard
wrote:
> These are exactly the steps to recreate the issue in 16.05 although I
> hit enter rather than clicking the checkout button (same thing though).
> Clin
These are exactly the steps to recreate the issue in 16.05 although I
hit enter rather than clicking the checkout button (same thing though).
Clint.
Owen Leonard wrote:
The error is
Can't use string ("1") as a HASH ref while "strict refs" in use at
/usr/share/koha/intranet/cgi-bin/circ/circulat
In my migrated koha system I have got to do many corrections and additions.
Some fields got values wrongly and some of the fields got no values. But
the source spreadsheet database has got correct values.
I was thinking about a method by exporting the biblio, items and
biblioitems tables to excel,
Hi,
You can use bc:35 to search particular barcode or use advance search.
On 26-Jan-2017 10:20 AM, "Tanzeem M.B" wrote:
When I search for a bibliographic record using advanced search with barcode
eg 35 I get all the records with barcode containing 35, ie 135,35, 3501
etc. how can I limit the se
When I search for a bibliographic record using advanced search with barcode
eg 35 I get all the records with barcode containing 35, ie 135,35, 3501
etc. how can I limit the search to getting the record with barcode exactly
matching "35" only?
___
Koha mai
A common thing on the holds-to-pull list is that the default limit for
holds to show on holds-to-pull is 2 days, you might consider upping the
default limit in the system preferences, or adding a filter that is
further back, which might catch a bunch of things you didn't know were
there!
Cheers,
L
Hi Liz,
Ah, okay. It's clearer to me now how to edit crons in the .hourly, .daily
folders. I thought it might have had something do with commenting out extant
entries and moving them elsewhere - thanks for clarifying! If "
build_holds_queue.pl " has nothing to do with posting holds to the "Hold
Hi Craig,
The cron job is run from files are in /etc/cron.hourly/koha-common for a
package install.
Note that "build_holds_queue.pl" doesn't affect the holds to pull. It
only affects the hold queue.
To change the frequency, you could comment out the job in
/etc/cron.hourly/koha-common, adding an
Salvete!
To add to what Barton said: if you've lingered in the new account queue,
1) email me,
2) prove you're not a terrible spammy bot,
3) and I will make sure that you get wiki access.
Cheers,
Brooke
___
Koha mailing list http://koha-commu
Hi Jonathan and all,
Currently using 16.05.07, an upgrade from 3.18. It was working fine before
the upgrade.
I was trying to search for a vendor in acquisitions. I typed in the vendor
name, pressed submit, and this error returned:
Can't use an undefined value as an ARRAY reference at
/usr/lib/p
The standard procedure is to sign up for a wiki account here:
https://wiki.koha-community.org/wiki/Special:RequestAccount
Then edit the page :-)
Cheers!
--Barton
On Wed, Jan 25, 2017 at 11:49 AM, Mark Alexander wrote:
> What is the standard procedure for reporting possible errors in
> wiki p
What is the standard procedure for reporting possible errors in
wiki pages?
The reason I ask is that during my attempts to install Koha from (1)
Debian packages, and (2) a git development environment, I have run
into a small number of commands or config file lines in the wiki pages
I used that I
Hi all,
Koha 16.05 on Ubuntu 14.04 LTS
Can someone confirm the name and location of the script that controls the
processing of hold requests? By 'processing' I mean when a patron clicks on
"Place Hold" from the OPAC, and then that request gets entered into the "Holds
to Pull" screen in the sta
> The error is
> Can't use string ("1") as a HASH ref while "strict refs" in use at
> /usr/share/koha/intranet/cgi-bin/circ/circulation.pl line 472.
My library has this problem too, in our production installation of 3.22.08.
1. Set the CircAutoPrintQuickSlip system preference to "clear the scree
Hi Barry,
From the kohastructure.sql file:
1350 -- this table is MyISAM, InnoDB tables are growing only and this
table is filled/emptied/filled/emptied...
1351 -- so MyISAM is better in this case
On Tue, 24 Jan 2017 at 15:24 Jonathan Druart
wrote:
> Hi Barry,
>
> From the kohastructure.sql fil
Hello Barry,
there is only one mention on choosing the MyISAM engine as I know: in
kohastructure.sql
-- this table is MyISAM, InnoDB tables are growing only and this table is
filled/emptied/filled/emptied...
-- so MyISAM is better in this case
Regards
Josef Moravec
Ășt 24. 1. 2017 v 14:55 odes
Hi Jane,
We need more information to help you.
What is the version of Koha you are using? How did you install it?
Is it a new error you get (after an upgrade) or just after you installed
Koha?
Then give us a step by step plan to recreate the issue, and if possible the
error you get in the Koha log
17 matches
Mail list logo