My Settings / Notification Settings page

Thanks, I've made some corrections to the code. Look for a new -dev snapshot.

I can't duplicate, but I'm guessing the problem is related to pre-exisiting users who have no entry in the notify table.

I changed it so that even when the warning is thrown, the settings form will still be displayed. Submitting the form will create an entry in Notify, so if my guess is right, it will solve your problem.

Hello,

I'v download this module in 5.X-2.X-dev version yesterday.

Got same bugs :

1° Only user #1 cant view his notification settings in user/1/notify (or by tab).
2° Message say "Your e-mail address must be specified on your my account page.".
3° The link in the message "my account" is to user/0/notify.

Did you patch this version ?
Regards.

Re open the case.

i had the same problem. No email sent and no acces to my account. The problem occured when i uninstalled the module and later installed it again. Before the modele worked perfect, after reinstalling the stable module it did nothing and gave the above errors. After i installed the (unstable?) dev version everything works oke.

Rene

I get the same error message ("Your e-mail address must be specified on your my account page.") when installing 5.x-1.2

Drupal 5.15
PHP 5.2.8

I wonder if this is related to this issue.
http://drupal.org/node/360729#comment-1208734

i have copied the above code in the module, doing the php-update but still the problem remains.

So i have reinstalled the dev-version again. It works, but gives a not secure warning.

Rene

There is a bug in function notify_user_settings_form():

  if ($user->uid != $arg->uid && $user->uid != 1) {
    drupal_access_denied();
    return;
  }

  $account = user_load(array('uid' => $arg->uid));
  if (!is_object($account)) {
    drupal_not_found();
    return;
  }

"$arg->uid" should be "$uid"

  if ($user->uid != $uid && $user->uid != 1) {
    drupal_access_denied();
    return;
  }

  $account = user_load(array('uid' => $uid));
  if (!is_object($account)) {
    drupal_not_found();
    return;
  }

then it works ...

It works. Thank you very much!!

Rene

elek's solution in #11 worked for me. Created a quick patch for it here.

patch reviewed & committed. Please test new dev release.

This issue has the same fix and maybe should be closed or marked as a duplicate.
http://drupal.org/node/360729#comment-1208734

Confirmed fix works on our system.

Looks to be fixed in current -dev, as well ;)