The newpot build command has a tendancy to cause more harm than good in
certain cases. Basically, if run with a translation-toolkit of 2.0+
after originally using 1.x, you end up with different POT formatting
which in turn breaks existing translations for those strings.
I talked this over with Ben Shum, and he advised we simply stop doing
POT updates in point releases for now. I agree, and this reversal is
my attempt to stop the bleeding. It tries to remove any unneeded POT
changes from recent history, while also keeping completely new strings
that have already snuck in.
This reverts commit a37154508d8fc078b5d9bae5ada105a534c13ecd.
This re-does commit 4e0b9d31cdbda3c356b22778b361ae4e60375255.
As with the XUL client, when performing a bib record TCN search
(Cataloging -> Retrieve Record By TCN), first look for non-deleted
records with the requested TCN. When none are found, perform a
secondary search for deleted records with the requested TCN.
To test in concerto:
[1] Navigate to Cataloging -> Retrieve Record By TCN
[2] Search for TCN value "10", which is deleted by default in Concerto.
[3] Confirm the deleted record is loaded.
LP#1788680 prevent copy template apply failure on null stat cats
Under some circumstances, the current code can result in a JS failure:
Cannot read property 'filter' of undefined
When this happens, the copy template may apply partially or not at all.
This change simply makes sure cp.stat_cat_entries() exists before
attempting to filter it.
Signed-off-by: Jeff Davis <email address hidden>
Signed-off-by: Dan Wells <email address hidden>
A missing return prevents a list of item ids from
being built so no holds can be placed from item
buckets. This branch returns the return to its
proper place.
To test
-------
[1] Add some items to an item bucket, ensuring that they are
all holdable.
[2] From the item bucket interface, select the items and choose
the Request Selected Items action.
[3] Confirm placing the requests.
[4] Note that the requests are not actually created.
[5] Apply the patch and repeat steps #1-#4. This time, the requests
should be placed.