warning notice on user save,

Notice: Trying to get property of non-object in multiple_email_var_replace() (line 809 of multiple_email.module

Comments

jthorson’s picture

Status: Active » Needs review

Confirmed.

jthorson’s picture

Status: Needs review » Active

Hmmm ... unable to reproduce again this evening ... not sure what might have changed in the meantime.

rakhimandhania’s picture

Hi, Thanks for reporting the issue. However, I am unable to reproduce this. Can you please provide some more details that can help?

vinoth.3v’s picture

StatusFileSize
new375.98 KB

Issue still exists.

vinoth.3v’s picture

Status: Active » Closed (cannot reproduce)

something makes this fixed. further user save working fine.

helmo’s picture

Status: Closed (cannot reproduce) » Active
StatusFileSize
new161.13 KB

I had this again after saving my user profile page ... after clinking the timezone link from #2090757: User timezone on git7site doesn't match the value on production

tvn’s picture

Status: Active » Needs review

Happened to me as well when updating timezone settings.

helmo’s picture

line 809 of multiple_email.module:

    '!username' => $account->name,

Which I guess we get to via multiple_email_user_update() ... but why is $account invalid?

jthorson’s picture

What's happening is $email comes through as a string, instead of as an object ... so the $email object references all trigger an error.

Once you save the user account once, the act of saving corrects the condition; and the notice thus disappears. This suggests it may be related to the update, perhaps within the multiple_email module.

helmo’s picture

Found an issue about this, with patch, #1809334: multiple_email_send_confirmation() called incorrectly

As drumm is maintainer getting this rtbc patch in should not be difficult.

tvn’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +drupal.org D7, +porting

That patch is in, tagging so we could get it on git7site.

drumm’s picture

Assigned: Unassigned » drumm
Status: Reviewed & tested by the community » Fixed

Merging to BZR and deploying now.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.