I received this bug report in email from Jonne Ylisuutari ... figured it was worth following up properly in the queue.
I noticed that the resource Conflict module ignores hidden date fields since it doesn’t create ['display']['default'] ['module'] value at all, but you can still check if a hidden field is date from other value. Here is a suggestion for code replacement:

in resource_conflict.module on row 206:

if (isset($field['display']['default']['module'])&&($field['display']['default']['module'] == 'date')&& ($field['required'] == 1)) {

change to

if (isset($field['widget']['module'])&&($field['widget']['module'] == 'date')&&($field['required'] == 1)) {

Off the top of my head, I seem to recall that testing based on the widget was also unreliable... and after all, people write custom widgets (and displays!) for their fields all the time. It would be nice to have a better way to test for a date field.

Comments

bkosborne’s picture

bkosborne
Primary language English
Location New Jersey, USA
commented
Issue summary: View changes
Status: Active » Fixed

OK I'm not sure why anyone was looking at display or widget settings, but I was able to determine if a field is a date field just by looking at the field_info_field data without introspecting those.

Fix has been commit.

Status: Fixed » Closed (fixed)

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