Bug 3744 - OPACAllowHoldDateInFuture description confusing

The missing syspref AllowHoldDateInFuture was added, and
OPACAllowHoldDateInFuture was moved next to it, on the Circulation
tab. Normally, it would go on the OPAC tab, but since both have to be
on for future holds on the OPAC, it's less confusing for them to be
together.
This commit is contained in:
Jesse Weaver 2009-11-03 21:09:16 -07:00
parent 3e88a7d738
commit 1abd0b56c2
2 changed files with 12 additions and 6 deletions

View file

@ -195,6 +195,18 @@ Circulation:
yes: Allow
no: "Don't allow"
- hold requests to be placed on items that are not checked out.
-
- pref: AllowHoldDateInFuture
choices:
yes: Allow
no: "Don't allow"
- hold requests to be placed that do not enter the waiting list until a certain future date.
-
- pref: OPACAllowHoldDateInFuture
choices:
yes: Allow
no: "Don't allow"
- "patrons to place holds that don't enter the waiting list until a certain future date. (AllowHoldDateInFuture must also be enabled)."
-
- Satisfy holds from the libraries
- pref: StaticHoldsQueueWeight

View file

@ -259,12 +259,6 @@ OPAC:
yes: Allow
no: "Don't allow"
- patrons to place holds on specific items in the OPAC. If this is disabled, users can only put a hold on the next available item.
-
- pref: OPACAllowHoldDateInFuture
choices:
yes: Allow
no: "Don't allow"
- "patrons to place holds that don't enter the waiting list until a certain future date (if AllowHoldDateInFuture is also on)."
-
- pref: OpacRenewalAllowed
choices: