This release modernizes the module’s integration points by introducing a clearer event flow for filtering and validating conflicts, and adds full test coverage for subscriber-driven overrides. Sites can now refine conflict lists, adjust validation, and attach errors to specific fields with far more control.
A large performance improvement if you use the same date field across multiple node types and potentially excluding some node types using that same conflict checking date field. And adding repeated date exceptions/additions won't trigger conflict checking unnecessarily
This version of the module now requires Date 2.x, and not Date 1.x. Be sure to update Date to the latest version before updating to Resource Conflict 5.x-2.1.
Changes since DRUPAL-5--2-0:
#336705: Upgrade Date API integration to work with Date 2 API.
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.
#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.
#265086: Document where the node reference module is available. #231148: Fix invalid arguments when you have multiple resource conflict content types set up. #251796: Fix default settings for node type form. Thanks!
