Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I installed this module and found out that at least on user register form the field is still visible (https://drupal.org/node/1970488). I simply used custom css so solve this... but what I found out additionally is that the customized decription is not used on any form.
This is caused by the lines 63 ff in spamicide.inc:
function _spamicide_get_description($lang_code=NULL) {
global $language;
$lang_code = isset($lang_code) ? $lang_code : $language->language;
$default = t('To prevent automated spam submissions leave this field empty.');
if (module_exists('locale')) {
$description = variable_get("spamicide_description_$lang_code", $default);
}
else {
$description = variable_get('spamicide_description', $default);
}
return $description;
}
I have the locale module activated as I manage a German project. I do not know where the variable "spamicide_description_$lang_code" should come from as nowhere in this module it is saved in this way. I use German as default.
Best,
Tobias
Comments
Comment #1
caspervoogt CreditAttribution: caspervoogt commentedIn my case the field is indeed hidden, but the customized message is not used. I have Locale and i18n on my site. So it seems to be looking for "spamicide_description_$lang_code" and not finding it. My temporary solution was to install https://drupal.org/project/stringoverrides and override "To prevent automated spam submissions leave this field empty." with my desired text. But the real solution would be for Spamicide's custom Description Message to work with Locale.
I did also look around in Variable Admin and /admin/config/regional/translate/translate, but could not find a variable to translate, so my only remaining options were hacking Spamicide or doing a string override.
Comment #2
boshtian CreditAttribution: boshtian commentedI see this is an old post but this problem is still not fixed. I think the correct way would it be to use Variable API using hook_variable_info, and from there on everything should be clear.