To get started, I found this error when I had my site set up according to the way I mentioned in #19 on this page: http://drupal.org/node/1637570 . Also, you can try this directly on my development site: http://www.spacesmovement.com . Please be nice and reserve the "Error checking" item only, as people are actually using the other ones! I created an example case arleady: view the WEEK of Feb. 10-16, 2013 at http://www.spacesmovement.com/reservation-calendar/63 to see an example of the bug.
So here's what I found, let's say that I create a reservation from 8-10 AM. Then I create a reservation from 7-11 AM. In other words, the new reservation dates are outside of the old reservation dates on both sides. The site simply creates the new reservation and does not throw an error. However, if either the start date, end date, or both either match or are inside of the old reservation, a conflict is detected and the site throws the appropriate error.
I am not enough of a coder to fix the problem, but my guess is that we need to add in something that not only checks for cases of the new dates being inside of the old dates, but also of old dates being inside the new dates. I think the term for this search is whether the old date "is between" either of the new dates.
Comments
Comment #0.0
laboratory.mikeAdding an example case of the bug mentioned in the issue.
Comment #1
laboratory.mikeI've solved the problem by using Rules instead of this module. I did this by adding a boolean field to reservations, and setting new reservations to "invalid." The rule checks the reservation against other reservations (using a VBO view to load potentially conflicting nodes), and if no conflict is found, the reservation is marked valid and published. If a conflict is found, it remains invalid, and is deleted at the end of the evaluation. At some point I hope to go a step further with Rules Forms so as to set a form error instead of having someone re-create the reservation.
Comment #2
bkosborneThe module should properly handle the case you outlined. The query that runs checks three different cases:
What is the date format of your date fields? Is it Date, Date ISO, or Date UNIX?
Comment #3
bkosborneClosing due to lack of response. Please re-open if you can provide more details, but that seems unlikely if you've already moved on to another solution.
Comment #4
wafaa.yousef commentedHi there,
I have the same issue and my date format is Date.
Thanks
Comment #5
joelpittetThis needs more information
Comment #6
joelpittetDrupal 7 reached its end of life in January 2025, and Resource Conflict no longer has an active D7 release. Development and support for D7 are not planned going forward, so we’re marking older D7 issues as outdated to help keep the queue focused on current versions.
If this issue is still relevant for Drupal 10+ or a new release line, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome! 💙