Problem/Motivation

Resource Conflict currently ignores smart_date fields. Editors
can create overlapping Smart Date ranges, including multi-value configurations,
without any conflict errors, which limits the module’s usefulness on sites that
standardize on Smart Date for scheduling.

Proposed resolution

Add integration for Smart Date so its field values are treated as one or more
time spans during conflict detection. Make Smart Date fields selectable in the
Resource conflict settings and apply the same conflict checks on node forms and
presave as for core Date range fields.

Issue fork resource_conflict-3558001

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

joelpittet created an issue. See original summary.

joelpittet changed the visibility of the branch 7.x-3.x to hidden.

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Active » Needs review

joelpittet opened merge request !4

  • joelpittet committed 2c25f4a9 on 2.x 
    feat: #3558001 Add support Smart Date (smart_date) fields
joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Needs review » Fixed

This was tricky due to the timestamp storage and lack of start_date or end_date properties, but in the end I think it's integrated well enough, hope someone can give it a try that cares to use smart_date. I am a date_recur maintainer so... bias is there.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.