When trying to change a reservation it is saying it can 't because there is a conflict but the conflicting time is it own previous revision.
All Current version
Drupal 6.25
Date 6.x-2.8
| Comment | File | Size | Author |
|---|---|---|---|
| ensemble046.png | 145.57 KB | iPeat |
When trying to change a reservation it is saying it can 't because there is a conflict but the conflicting time is it own previous revision.
All Current version
Drupal 6.25
Date 6.x-2.8
| Comment | File | Size | Author |
|---|---|---|---|
| ensemble046.png | 145.57 KB | iPeat |
Comments
Comment #1
iPeat commentedusing Calendar View, Inventory, Role Rule Override, Staff, and Template Merci modules
Comment #2
iPeat commentedseems to be connected to revisions If I delete the old revisions it will save with no conflict
Comment #3
darrick commentedThat was my guess. Thanks for the report. It will take me a few days to come up with a fix.
Comment #4
iPeat commentedSeems sporadic as well but I think I have it narrowed down to the third change with a specific item selected so:
confirm, check out, check in (no errors)
However:
confirm, confirm with items selected, checkout, Check in (Error)
confirm, confirm additional item added, confirm with items selected, checkout, Check in (Error)
confirm,confirm (with items selected), confirm additional item added , confirm with second item selected (Error)
Comment #5
iPeat commentedTemporary band aid
As long as you are using the ajax validation via Merci Staff, you should never see the conflict grid anyways.
Just comment out lines 100 to 104 in api.inc
Comment #6
darrick commentedCan you try this patch and see if it works for you?
http://drupalcode.org/project/merci.git/patch/48abfd0
Comment #7
iPeat commentedThe patch seems to be functioning properly.
Thanks for looking at this so quickly with
Comment #8
iPeat commentedComment #9
iPeat commentedAlmost there.
Here is the new scenario:
Item is checked out for a full day it comes back early and is checked in.
New reservation is created that item is available and selected. Conflict grid error appears.
Correct the to time on the checked in reservation. Still errors
Delete revisions of the checked in reservation. Works fine
Comment #10
darrick commentedI've fixed the bug in #9 here: http://drupalcode.org/project/merci.git/patch/1cd1e3f
The bug happens whether or not revisions are used. The conflict code was not checking the status of the reservation (i.e. Pending, Reserved, Checked Out, Checked In) only the time the item was reserved.
Also if revisions were being used the code was looking up the most recent revision.
Comment #11
iPeat commentedInitial testing looks good
Comment #12
darrick commentedIn light of your other issue #1512294: Double Check out Error I'm inclined to revert my fix in #10. As ideally when a reservation is checked back in the staff will correct the checkin date.
Comment #13
iPeat commentedWe charge for late fees so changing the date due when it comes back isn't something we do. I don't understand why this is ideal, seems like it would skew usage data? I created a separate Checked in date field that is auto completed via a triggered rule on changing the status to Checked in. Anyway seems to be mute see #1512294: Double Check out Error Haven't seen any other issues regarding the conflict grid
Comment #14
darrick commentedOkay. I'll hold off on reverting in light of the recent fixes for the other issues.
Comment #15
darrick commented