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.
Seems that does not exist any configuration form in order to set this variable or i am missing something ?
Related function:
/**
* Implements hook_flag().
*
* When flagging subscription flags, check if user wants email notifications
* and flag the user for emails accordingly.
*/
function message_subscribe_email_flag($action, $flag, $content_id, $account) {
$prefix = variable_get('message_subscribe_flag_prefix', 'subscribe') . '_';
if (strpos($flag->name, $prefix) === 0) {
// The flag is a subscription flag.
$wrapper = entity_metadata_wrapper('user', $account);
if ($wrapper->message_subscribe_email->value() || $action == 'unflag') {
// User wants to use email for the subscription.
// Flag or unflag user for emailing according to action taken.
$name = str_replace($prefix, '', $flag->name);
flag($action, 'email_' . $name, $content_id, $account);
}
}
}
Comments
Comment #1
paolomainardi CreditAttribution: paolomainardi commentedSeems to be something related to "commons_notify" features.
Can you confirm this ?
Comment #2
paolomainardi CreditAttribution: paolomainardi commentedUp
Comment #3
amitaibuThat field is added in message_subscribe_email_install()
Comment #4
paolomainardi CreditAttribution: paolomainardi commentedYou're right, my fault, sorry.
Thanks a lot Amitaibu!
Comment #6
sysopx0 CreditAttribution: sysopx0 commentedamitaibu - I installed the module and that field wasn't created. After that, Drupal crashes everytime when subscribing.
Comment #7
sysopx0 CreditAttribution: sysopx0 commentedI suspect the error related to the inexistence of the message_subscribe_email field is caused by the fact that the list module is not registered as a prerequisite for the message_subscribe_email submodule. If the list module is enabled before that module is created then that field gets created in the user entity (as a boolean). Otherwise, it will give you an error, since that boolean sub-type only exists in the list module.