cannot select: fields to check for conflicts
deemuzi - February 27, 2008 - 10:36
| Project: | Resource Conflict |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I cannot select option in "Fields to check for conflicts:" box.
I created new cck named "car" and "reservation". Reservation has event enabled and node reference field. I selected cars in "Fields to check for conflicts" option box and save my cck configuration, but after I try to re-edit reservation cck I see that all options are unselected.
Maybe it depends on my configuration because I have a lot of modules installed, but resource conflict doesn't work for me.
#1
I installed new drupal testing site with only cck, event, node reference and resource conflict module, and it's works
#2
Glad you got it working. If you find the module it was conflicting with, please let me know and I'll see what can be done to fix it.
--Andrew
#3
I'm now seeing this problem.
Drupal 5.5
List of enabled modules below for your reference:
mysql> select name from system where type='module' and status='1';+-------------------+
| name |
+-------------------+
| system |
| activeselect |
| block |
| blog |
| book |
| collapsiblock |
| color |
| comment |
| ermm |
| ermmasset |
| ermmprofitability |
| ermmtraining |
| ewiki |
| filter |
| forum |
| help |
| isr |
| jstools |
| ldapauth |
| ldapdirectory |
| ldapgroups |
| legacy |
| menu |
| node |
| path |
| profile |
| replication |
| search |
| servicecentre |
| status |
| tabs |
| taxonomy |
| tinymce |
| user |
| watchdog |
| ldapdata |
| servicestatus |
| dapi |
| erm |
| ermasset |
| ermcommerce |
| ermtraining |
| eservglobal |
| nodeaccess |
| dbfm |
| taxonews |
| basicevent |
| event |
| event_all_day |
| event_views |
| og |
| og_calendar |
| views |
| views_rss |
| views_ui |
| dbfmgreybox |
| rsvp |
| diff |
| resource_conflict |
| content |
| nodereference |
+-------------------+
61 rows in set (0.00 sec)
#4
#5
After you submit the form, are there any resource_conflict variables in your variables table? They should be set auto-magically as 'resource_conflict_'.
If you can, please disable modules and try to narrow down one which is causing a conflict, assuming a module conflict is the source of the bug.
Thanks,
--Andrew
#6
I'll take another look as time permits.
#7
I'm wondering if you were being hit by #295571: Long content type names exceed the maximum variable length on Drupal 5. If the total variable length was longer than 48 characters, things would have broken. You're welcome to try out the 2.x branch, but be warned that it doesn't have an upgrade script yet, so you'll have to redo the resource conflict settings.
--Andrew
#8
I'm marking this as closed as there hasn't been any updates on this in quite a while. Please re-open if you have more information.
--Andrew