Duplicate Key Error if you event-enable and conflict-enable a type which contains date fields
deviantintegral - July 31, 2008 - 04:10
| Project: | Resource Conflict |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
If both date fields and events are active on a content type, you can no longer submit the workflow form. The only way I could get past the error was to delete the content type entirely, and create a new one. We should provide a way to let users choose the field if both are present, or at the very least prevent the error and require the content type to have dates or event.
--Andrew
#1
This has been fixed in CVS #134058. I haven't been able to reproduce the actual error, likely due to other changes in the code. However, you can now have both dates and event on a content type and be able to choose which field to check, without being locked into date.
--Andrew
temp
Automatically closed -- issue fixed for two weeks with no activity.
#2
Automatically closed -- issue fixed for two weeks with no activity.