Hey, folks. Here's what happens on my test site.

1. Installed and turned on all SMS Framework modules (except Muse and Clickatell).

2. As admin, went to my /user page. Clicked "Mobile settings".

3. Entered my 10-digit U.S. phone number (no dashes, spaces, or country code) and carrier.

4. Clicked "Confirm number".

5. Went to the confirmation page, but got the following error, and no confirmation SMS.


    * warning: Attempt to assign property of non-object in /Users/tgeller/Sites/dru6_brevity/sites/default/modules/cck/includes/content.token.inc on line 9.
    * warning: Attempt to assign property of non-object in /Users/tgeller/Sites/dru6_brevity/sites/default/modules/cck/includes/content.token.inc on line 10.
    * warning: Attempt to assign property of non-object in /Users/tgeller/Sites/dru6_brevity/sites/default/modules/cck/content.module on line 334.
    * warning: Invalid argument supplied for foreach() in /Users/tgeller/Sites/dru6_brevity/sites/default/modules/cck/includes/content.token.inc on line 18.

Any ideas?

Thanks,

--Tom

CommentFileSizeAuthor
#8 sms_user_confirm_token_5.x-1.x-dev.patch626 bytesmatt@antinomia
#8 sms_user_confirm_token_6.x-1.x-dev.patch574 bytesmatt@antinomia

Comments

Will White’s picture

Will White commented

Hey Tom,
Try disabling the CCK module and test it then. I'm not sure what's going on here. I'll install CCK and see if I can reproduce this. Thanks!

tgeller’s picture

tgeller commented

Hey, Will. I actually don't have CCK installed on that site. I created it just to test the SMS framework, and have only that module, token, and poormanscron installed.

By the way, I now don't know what I meant by "Went to the confirmation page", above, or how to reproduce that error. Now when I go to user/1/mobile, click "Delete & start over", and try again, I just come back to that user/1/mobile page. *shrug*

Cheers,

--Tom

Will White’s picture

Will White commented
Title: Can't confirm phone number » CCK Error during number confirmation

Hey Tom,
As you can see from the message you received the errors are occurring in content.token.inc and content.module, both of which are a part of the CCK project. It would have to be installed on your site for those files to cause errors.

I know you said that you were not able to reproduce the error, but are you able to receive the confirmation messages on your phone now? Thanks!

tgeller’s picture

tgeller commented

Hey, Will -- thanks for the quick reply. I now see from this issue's title that I must have had CCK installed at the time that I first got the error. Heh. I don't know what happened between now and then... maybe I was testing it on a different installation? *shrug*

In any case: No, I'm not getting the confirmation message on my phone.

Let me know what I should do (install the devel module?) to give you useful log info. Thanks again!

--Tom

Will White’s picture

Will White commented

Which carrier are you trying to send to? I know I have elusive problems with Verizon. I'd love to get those worked out but I have AT&T personally so I haven't been able to test.

tgeller’s picture

tgeller commented

I'm on Verizon and would be happy to test. :) Would you like to try doing a "sprint" some time by phone/IM/Skype?

matt@antinomia’s picture

matt@antinomia commented

Having the same issue here with 5.x-1.x, although the confirmation code is being sent in my case. Disabling CCK does fix the problem, but I don't see where/how CCK has anything to do with confirming your SMS number.

matt@antinomia’s picture

matt@antinomia commented
StatusFileSize
new sms_user_confirm_token_6.x-1.x-dev.patch574 bytes
new sms_user_confirm_token_5.x-1.x-dev.patch626 bytes

The problem seems to be an improper argument in the call to token_replace_multiple() within _sms_user_confirm_message(). I'm attaching patches for both 5 & 6 that modifies the token_replace_multiple() call to use the proper array for the 'types' argument.

matt@antinomia’s picture

matt@antinomia commented
Status: Active » Needs review
tgeller’s picture

tgeller commented

Still doesn't work, I'm afraid. :( It may be a conflict with the SMTP Authentication module, which my ISP requires to send mail via a Web application.

The (anonymized) log error is: 

Error sending e-mail from user@example.com to 4155551212@vtext.com : SMTP Error: Could not connect to SMTP host.

Ideas?

matt@antinomia’s picture

matt@antinomia commented

The patch _does_ fix the "CCK error during number confirmation" error that this ticket was opened for. Sounds like you need to configure the SMTP Authentication module to use the right server/login details. Have you properly configured that module?

tgeller’s picture

tgeller commented

I have properly configured that module -- The test email works, and I can send email elsewhere on the site (through the Contact form, for example).

matt@antinomia’s picture

matt@antinomia commented

In that case, it may be that there's another issue in the 6.x branch. I'm still using 5.x-1 so it's hard for me to say. Any thoughts Will?

Will White’s picture

Will White commented

@matt: Thanks for the patch. I'll review that shortly.

@tgeller: I'm almost positive that the problem relates to using Verizon as a carrier. I've never been able to successfully send a message to a Verizon phone. All of the online resources that say Verizon's gateway address is tendidgetphone@vtext.com, but it doesn't seem to work (as your error message shows). Can you try sending a message to your phone from your normal email client?

tgeller’s picture

tgeller commented

Hey, Digger. Yep, I tried sending an message to my phone through a standard email client, and it worked fine. 'tis a puzzlement.

matt@antinomia’s picture

matt@antinomia commented

FWIW, I've successfully used the Verizon gateway with version 5.x-1.

Will White’s picture

Will White commented
Status: Needs review » Fixed

Committed the patch. Please create a new issue for about Verizon if necessary. Thanks!

http://drupal.org/cvs?commit=144906

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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