Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.From xmacinfo: "For each event I'm using the same resource, But the system never send a warning when a resource is already used. So I think it does not check for date conflicts."
My guess is that this has to do with Date 2 being used instead of Date 1.
Comments
Comment #1
marcvangendI see the same problem here. I'm running Drupal 6.8. Modules installed: Calendar 6.x-2.x-dev, CCK 6.x-2.1, Date 6.x-2.0-rc6, Resource Conflict 6.x-2.x-dev (2008-Dec-11), Views 6.x-2.1 (and a couple of others that probably don't matter or this issue).
If I find some time, I'll try to find out where it goes wrong.
Comment #2
marcvangendI can confirm now that changes in the date2 API are the cause of the problem. The date_make_date() function was changed (it now takes 3 params instead of 4) and the date_show_value() function was completely dropped. I was able to make the module work on my site with some quick changes to the code. In fact, it only involved the correct converting to and from ISO-formatted time strings, datetime objects and timestamps at various places in the code. I'm not posting code or patches yet because I haven't properly tested it (ie. with timezones).
Maybe it would be wise to decide on one single format to pass dates around between the functions (the native php datetime object seems like a logical choise to me). Inside the functions, the date api and regular php can be used to perform conversions for use in queries and for on-screen display.
Comment #3
tannerg commentedI'm also having trouble with this.
I'd be interested to get some more details on the changes you made to get this working.
Comment #4
zirvap commentedIf you post code or patches I'd be happy to help testing.
Comment #5
deviantintegral commentedI believe this is fixed as part of the work over at #336705: Upgrade Date API integration to work with Date 2 API, so please test the patch there.