[koha-commits] main Koha release repository branch master updated. v3.18.00-593-gc16e19b

Git repo owner gitmaster at git.koha-community.org
Wed Apr 8 16:35:06 CEST 2015


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, master has been updated
       via  c16e19b3fdff71e20db1df036931d96dfabcce4d (commit)
       via  b3183f16e55f251003583a741b06bdfa635b1f07 (commit)
       via  2a8f84817fb4a487577c7e4238b8aede9d9b99d2 (commit)
       via  80ffd8354bff15ef006da746ce516f6e9b497dc5 (commit)
       via  ab326b368b1eb715b3a203dcb0edc88de59a0fac (commit)
       via  56a147da32492954a2a417a5e4f3766ae734f45a (commit)
      from  0526eb4dfb14f81fe27e1499adfa18559de03a21 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c16e19b3fdff71e20db1df036931d96dfabcce4d
Author: Jonathan Druart <jonathan.druart at biblibre.com>
Date:   Mon Mar 30 17:04:27 2015 +0200

    Bug 7561: Redirect to the add items form if it's a fast cataloging
    
    Signed-off-by: Nicole Engard <nengard at bywatersolutions.com>
    
    Signed-off-by: Katrin Fischer <katrin.fischer.83 at web.de>
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit b3183f16e55f251003583a741b06bdfa635b1f07
Author: Jonathan Druart <jonathan.druart at biblibre.com>
Date:   Mon Mar 30 13:17:26 2015 +0200

    ug 7561: Fast cataloging - Allow add/edit items and delete record
    
    With the fast cataloging permission, a librarian was not able to
    add/edit items and to delete a record with the FA framework.
    
    This patch fixes that.
    
    Test plan:
    0/ Set the permission fast_cataloging (and only this one under
    editcatalogue) to a librarian
    1/ Log in with this account
    2/ Go to Circulation > Fast cataloging
    3/ Confirm you can create a record
    4/ Save and confirm you can create items
    5/ Confirm you are able to edit items, remove all of them and delete the
    record.
    6/ Make sure it only works for records with the FA framework code.
    
    Signed-off-by: Nicole Engard <nengard at bywatersolutions.com>
    
    Signed-off-by: Katrin Fischer <katrin.fischer.83 at web.de>
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit 2a8f84817fb4a487577c7e4238b8aede9d9b99d2
Author: Jonathan Druart <jonathan.druart at biblibre.com>
Date:   Tue Mar 31 16:32:33 2015 +0200

    Bug 8246: Allow deleting record if no more items
    
    The "Delete records if no items remain" was only available if the batch
    did not contain "too many" items (see MaxItemsForBatch).
    This limitation does not make any sense.
    
    Test plan:
    1/ Set MaxItemsForBatch=10
    2/ Use the batch item deletion to delete 10+ items
    3/ Confirm the checkbox "Delete records if no items remain" is displayed
    4/ Check it
    5/ Launch the job
    6/ Run koha qa test tools
    
    Verify that the records without items have been deleted also.
    
    NOTE: My test db only had two biblios with items, so I set
          MaxItemsForBatch=1.
          Before patch, checkbox did not display.
          After patch, checkbox did display.
          This patch merely moves one line out of the IF/ELSE/END
          block, and reindents for more readability. Though, there
          is a missing <p> if you want to get picky.
    
    Signed-off-by: Mark Tompsett <mtompset at hotmail.com>
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit 80ffd8354bff15ef006da746ce516f6e9b497dc5
Author: Abby <abbyrobnz at gmail.com>
Date:   Mon Feb 16 15:45:16 2015 +0100

    Bug 10887: Batch item deletion -- doesn't need Use default values section
    
    To test:
    1. Go to Home > Tools > Batch item deletion
    2. Notice that there is an unnecessary option for "use default values
    section" to "Populate fields with default values from default work"
    3. Apply the patch.
    4. Check that this section has disappeared.
    
    Signed-off-by: Nick <Nick at quechelibrary.org>
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit ab326b368b1eb715b3a203dcb0edc88de59a0fac
Author: Katrin Fischer <Katrin.Fischer.83 at web.de>
Date:   Mon Mar 23 21:42:14 2015 +0100

    Bug 13380: Follow-up - only run database update, when it hasn't been run already
    
    As the ORDER_CANCELLATION_REASON authorised value has been
    backported to 3.18.5, we need to make sure that the database
    update is only run once.
    
    This patch adds a check for the existance of the authorised
    value in order to decide if the databaes update can be run.
    
    To test:
    - Create a branch 3.19.00.016
    - Make sure you have a few orders where the cancellationreason
      is set (cancel an order, enter a reason)
    - Update your branch to master + this patch
    - Run the web installer
    - ORDER_CANCELLATION_REASON authorised value category is created
    - Reset your system preference Version to 3.19.00.015
    - Run database update again - no changes are made, all is fine
    
    Or:
    - Create a branch 3.18.04 with cancelled orders
    - Update to latest 3.18.x
    - Make sure ORDER_CANCELLATION_REASON has been created
    - Dump database
    - Switch to master without this patch
    - Run update - verify more O_C_R were created (bad)
    - Load database
    - Update to master with this patch
    - All should be fine
    
    Signed-off-by: Jonathan Druart <jonathan.druart at biblibre.com>
    
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>

commit 56a147da32492954a2a417a5e4f3766ae734f45a
Author: Jonathan Druart <jonathan.druart at biblibre.com>
Date:   Fri Mar 27 17:30:01 2015 +0100

    Bug 7480: Don't display current logged in user as basket manager
    
    The "Managed by" field displayed on creating/editing an order is always
    the name of the logged in user.
    
    To reproduce:
    1/ Log in with patron A
    2/ Create a basket
    3/ Create an order
    4/ Log in with patron B
    5/ Edit the order
    6/ The "Managed by" line is "patron B"
    
    Test plan:
    Apply the patch and confirm that the "patron A" is always the basket
    manager.
    
    Followed test plan. Works as expected.
    Signed-off-by: Marc Véron <veron at veron.ch>
    
    Signed-off-by: Katrin Fischer <katrin.fischer.83 at web.de>
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

-----------------------------------------------------------------------

Summary of changes:
 acqui/neworderempty.pl                             |    1 -
 cataloguing/addbiblio.pl                           |    7 ++-
 installer/data/mysql/updatedatabase.pl             |   59 +++++++++++---------
 .../intranet-tmpl/prog/en/includes/cat-toolbar.inc |   18 +++---
 .../prog/en/modules/cataloguing/addbiblio.tt       |    2 +-
 .../prog/en/modules/tools/batchMod-del.tt          |    9 ++-
 .../prog/en/modules/tools/batchMod.tt              |   24 ++++----
 7 files changed, 67 insertions(+), 53 deletions(-)


hooks/post-receive
-- 
main Koha release repository


More information about the koha-commits mailing list