Resource Conflict becomes unticked
rex_the_first - November 4, 2009 - 16:33
| Project: | Resource Conflict |
| Version: | 6.x-2.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Description
On the edit content type the
Fields to check for conflicts
tick box keeps becoming unticked. I am not sure how to log/track this but it is ticked then a month later when I go back to it after complaints of double bookings it has become unticked. Could you advice?
#1
Also the message that resource conflict has been switched off does not appear in the system log
I get this php error in the system log:
strtr() [function.strtr]: The second argument is not an array in /home/greenaction/thepeanutgallery.org.uk/modules/syslog/syslog.module on line 106.
(line 106 in syslog is
<?php$message .= '|'. strip_tags(is_null($entry['variables']) ? $entry['message'] : strtr($entry['message'], $entry['variables']));
?>
)
at the same time I get Resource Conflict tries to send this:
Resource Conflict has been disabled for the event content type as the requirements for it are no longer met.
I am not sure but it looks like the watchdog message is not in the correct format but I cannot see any problem.
(from resource_conflict.module)
<?php$msg = t('Resource Conflict has been disabled for the %type content type as the requirements for it are no longer met.', array('%type' => $type));
watchdog('rsrc conflict', $msg, WATCHDOG_WARNING);
?>
See http://drupal.org/node/349259 for something that *might* be related.
#2
More info on Resource Conflict becoming un-ticked.
This happens when Captcha module stops some spam.
event_node_form post blocked by CAPTCHA module: challenge "Random CAPTCHA type" (by module "random_captcha_type"), user answered "reCAPTCHA", but the solution was "1".
Could this trigger Resource Conflict to switch off?
I am going to disable function _resource_conflict_disable for now
#3
Commenting out the function _resource_conflict_disable has stopped the problem. I will have a look at fixing this but I don't know much php.
#4
Well, there's a bug in that Watchdog call; the message doesn't need to be piped through t() as watchdog does that for you. That's likely the cause of your error from the syslog module. However, I think it's likely unrelated to the issue of it becoming disabled. I'll try and install recaptcha this weekend to take a look.
#5
Here's a patch with the Watchdog call fixed. I've installed recaptcha, and with this patch everything seems fine. Can you give it a test and let me know if it works for your install as well?
Thanks!