resource_conflict 5.x-2.0

This is a pretty significant release, implementing Date API compatibility as well as many bug fixes and user interface improvements. Conflicts can be detected between content types using both the Date API and the Event module. The process for setting up the appropriate content types and the required fields is much clearer, and Resource Conflict detects when it can't be enabled and informs the user why.

Many thanks goes to dww for setting up sponsorship, and for his code contributions to this release.

• #289350: Implement upgrade from version 1 to version 2: Implement upgrade from version 1 to version 2
• #289341: Warning if no resources have been created: Warning if no resources have been created
• #295568: Implement hook_uninstall to clean up variables.: Implement hook_uninstall to clean up variables.
• #295075: Usability: display all resource conflicts simultaneously and provide links: Fixed bug where not all resource conflicts were printed simultaneously. Due to limitations in FAPI, we need to make sure we pass a unique key to form_set_error() for every resource/event pair.
• #289346: Dates have to have a required end fields: Dates have to have a required end fields. If the requirements for resource conflict are detected to fail on the workflow form or on the node edit form, warn the administrator and disable completely until it is fixed and re-enabled.
• #289344: Duplicate Key Error if you event-enable and conflict-enable a type which contains date fields: Duplicate Key Error if you event-enable and conflict-enable a type which contains date fields. The actual error was fixed in an earlier revision, but this set of changes makes handling content types with both date fields and event much easier to user.
• #295075: Usability: display all resource conflicts simultaneously and provide links: Usability: display all resource conflicts simultaneously and provide links. Also reverted previous change to rc_types storage as the error no longer exists. Ensure that all nodes checked are unique.
• #289338: Clean up messages and errors: Clean up messages and errors. Also fixed a minor bug from renaming the variables in #295571.
• #289348: Events can no longer have the same end / start times: Events can no longer have the same end / start times. This was actually much more serious causing all kinds of issues as the end time wasn't being passed properly.
• #295571: Long content type names exceed the maximum variable length on Drupal 5: Long content type names exceed the maximum variable length on Drupal 5.
• #294578: Unknown field DB error when creating reservation nodes if the date field is in a separate table: Fixed table prefix bug introduced in revision 1.1.2.5.2.3.
• #294578: Unknown field DB error when creating reservation nodes if the date field is in a separate table: Allow CCK fields to exist in a seperate table for cases where a field is used in more than one content type.
• #294594: Fix code style errors: Code style cleanup fixes by dww.
• #231445: Work With Date API: Work with date API. New features include better code structure and cross-api integration between events and dates.
• #251796: No default values for node reference fields: Fix default settings for node type form. Thanks!
• #231148: warning: Invalid argument supplied for foreach() in...: Fix invalid arguments when you have multiple resource conflict content types set up.
• #265086: Document where to get nodereference module: Document where nodereference can be found.
• #182858: Error editing a reservation: Fixing issue with ending event times.
• #182858: Error editing a reservation: Fixing incorrect use of db_fetch_array so that multiple results can properly be returned.
• #178897: Node creating error messages: Fixing errors with NULL or FALSE returns for variables used in foreach() loops. Added and cleaned up a few comments. When updating an existing node, bookings no longer conflict with themselves.