Galen Charlton [Wed, 17 Mar 2010 00:02:31 +0000 (20:02 -0400)]
Merge branch 'Bug3482' of git://github.com/ptfs/Koha-PTFS into to-push
* 'Bug3482' of git://github.com/ptfs/Koha-PTFS:
Bug 3482: Updated DB version
Bug 3482 changed name of notices file
Bug 3482 Allow hold notices to be sent in print form
Add expiration date, today to hold notices
Modified to use dirspec only
Bug 3482 Print Notices via HTML
Jesse Weaver [Thu, 11 Jun 2009 20:49:15 +0000 (14:49 -0600)]
Bug 3482 Allow hold notices to be sent in print form
This is done by saving the notices in the message_queue table with
type 'print'. The notices are generated from a notice named
HOLD_PRINT. At the end of the day, they are dumped to an HTML file and
marked as sent by a new cronjob.
This setup is intended to be temporary; modules/batch/ shouldn't be around
forever.
Mandatory SQL:
INSERT INTO message_transport_types (message_transport_type) values ('print');
Kyle M Hall [Mon, 22 Feb 2010 15:21:31 +0000 (10:21 -0500)]
Bug 3482 Print Notices via HTML
Modified overdue_notices.pl to support output of html for printing.
The -html option will e-mail notices to those with e-mail, and output
html to print for borrowers without e-mail.
When system preference PrintNoticesMaxLines is set to a positive
integer, it will limit the number of items on the notice to that
number, and append a message to the end telling the borrower to
check his or her account for the full listing of items. This only
affects print notices, not emailed ones.
Mandatory SQL:
INSERT INTO `systempreferences`
( `variable` , `value` , `options` , `explanation` , `type` ) i
VALUES ( 'PrintNoticesMaxLines', '0', '', i
'If greater than 0, sets the maximum number of lines an overdue notice will print. If the number of items is greater than this number, the notice will end with a warning asking the borrower to check their online account for a full list of overdue items.',
'Integer' );
Owen Leonard [Wed, 10 Feb 2010 21:18:58 +0000 (16:18 -0500)]
Fix for Bug 2970, Create a permission for modifying holds priority
Adding two new granular permissions under 'reserveforothers,' place_holds
and modify_holds_priority. If a user does not have modify_holds_priority
permission, the option to change the priority of a hold is hidden.
Revised patch includes changes to mandatory data files including
properly translated fr-FR version.
Galen Charlton [Fri, 19 Feb 2010 03:42:53 +0000 (22:42 -0500)]
bug 1532: various code cleanup
* export C4::Reserves::CancelExpiredReserves
* rename misc/cronjobs/cancel_expired_reserves.pl
to misc/cronjobs/holds/cancel_expired_holds.pl
* added cancel_expired_holds.pl to example crontab
* fix staff crash if AllowHoldDateInFuture is on
* expirationdate is now nullable instead of relying
on 0000-00-00
Galen Charlton [Fri, 19 Feb 2010 02:45:56 +0000 (21:45 -0500)]
bug 1532: tweak new reserves columns and add to init SQL (DB rev 121)
Changed type of lowestpriority from BOOL to tinyint(1) - BOOL was likely
OK, but made it tinyint(1) to match the rest of the flag columns. We
should look into converting those to BOOL en masse in 3.4.
Kyle M Hall [Wed, 23 Sep 2009 16:10:23 +0000 (16:10 +0000)]
(bug 1532) Reserves Updates Ported From Dev_Week
This is a much improved re-implementation of the reserves updates from dev_week.
Less new code has been added, and more existing functions are used instead of adding new ones.
The 'Lock Hold' function has been removed due to it not working as intended.
[RM note for documentation: this adds the following features:
* ability to specify an expiration date for a hold request
when placing it via the staff interface or OPAC
* daily batch job to cancel expired holds
* nice interface to change the priority of hold
requests for a bib in the staff interface]
Michael Hafen [Wed, 4 Nov 2009 21:31:48 +0000 (14:31 -0700)]
bugfix Guided Reports - allow user specified limit in sql
Tweak the regular expression in strip_limit to work.
Tweak execute_query to use the user limit if it's lower than the hard coded one.
Also total is calculated somewhere else now.
This helps most with the csv export of a report so the user can set their own
limit instead of having the hard coded limit of 9999.
Michael Hafen [Wed, 18 Nov 2009 15:37:40 +0000 (08:37 -0700)]
add memcached questions to koha-install-log
Add the use_memcached question to rewrite-config.pl and all three questions
to koha-install-log. So that we don't have to keep answering these questions
when we upgrade/install with the --prev-install-log option.
Galen Charlton [Thu, 18 Feb 2010 18:22:46 +0000 (13:22 -0500)]
Revert "Add basic restrictive robots.txt file to opac"
Per discussion on 12/9/2009, reverting. I agree with Nicole Engard
that a restrictive robots.txt for the OPAC should *not* be the
default. A patch for a README on how to do it would be nice, though.
In one of my setups, "install-code.pl pt-PT" complained
about a missing "Locale::PO". So, I'm adding it to
Makefile.PL. I'm using the version 0.17 as minimum
required because it's the one that's available in
Debian 5.0.2. ("lenny").
this patch restrict the send of baskets and shelves to authenticated users only, and show their surname/firstname in the e-mail, so the receiver will know who sent the list.
(cherry picked from commit f87b75522801ee6d08291bb0eeb6bc38a5b785d5)
Jane Wagner [Thu, 18 Feb 2010 16:45:50 +0000 (11:45 -0500)]
Bug 4215 OPAC "Search for title in" can fail with trailing slashes in title
While configuring Search for Title In links, I found that some target sites
can't process an incoming title search if the title being sent has a trailing
slash. If the same search is sent without the trailing slash, it works fine. I
modified opac-detail.pl to strip off the trailing slash (and space) for titles
being sent to other sites.
projects / koha.git / log