Dates have to have a required end fields
deviantintegral - July 31, 2008 - 04:14
| Project: | Resource Conflict |
| Version: | 5.x-2.x-dev |
| Component: | Documentation |
| Category: | bug report |
| Priority: | normal |
| Assigned: | deviantintegral |
| Status: | closed |
Jump to:
Description
I haven't tested it yet, but I imagine a line like '$end = $node-> {$date_field}[0]['value2'];' would cause problems if the end date was optional or missing. Such a situation should be detected on the workflow form as a requirement to enable resource conflict, and handled gracefully on node edits.
--Andrew
#1
I've fixed this issue by detecting when the requirements have been changed after the fact in the workflow form and on the node edit form, and disabling resource conflict.
--Andrew
#2
Automatically closed -- issue fixed for two weeks with no activity.