SMS framework and notifications

I was having the same issue and I can't remember exactly what I did to fix it but I know in I made the following changes

sms_user.module
Line 431

-    $user_data = unserialize($account->data);
+    $user_data = $data;
-    $account->sms_user = $user_data['sms_user'];

sms_email_gateway.module
Line 194

-  $to = $number .'@'. $options['carrier'];
+  $to = $number['number'] .'@'. $number['gateway']['carrier'];

and it works for me.

I was having an unserialize error message and a few other problems which made me switch between various versions of this module messaging and notifications.

I'm using the email gateway with the following versions
Messaging 6.x-4.x-dev (2011-Jun-12)
Notifications 6.x-4.x-dev (2011-Feb-26)
SMS Email Gateway 6.x-1.0
SMS Framework 6.x-2.x-dev (2011-Mar-30)

Did you install all of them at once or one at a time. If you tried to install all of them at once go back and try them one at a time and see which one gives you the WSOD. That should help narrow it down a little bit.

I have only received the WSOD a couple times and by deleting the last module I installed and then checking the recent log or the server log I was able to track it down.

I hope this helps.

Is the alpha version working for you or are you still having the same problem?

mrweaver, did you finally solve this issue because I'm on the same boat with my sms gateway for about a year now and I'm stuck. How did you get the name of the gateway identifier and which line is that?

charos,

Mine isn't working anymore. I tried both of the options I had listed above and it just will not pass the carrier info to the sms email gateway. I know it is there because I am able to receive the messages when I add the phone number to the account but I cannot receive any messages after that through sms.

mrweaver, can you be a bit more specific on which line you are referring to and what replacements you did? I've read your post #10 several times but I can't figure it out.
I think it will help also to post the module(s) version you are using!

Thanks!

Thanks for the reply.
I'm using Clickatell gateway module and have same issues with Notifications. So I'm trying to figure out what to change in my case to make it work. If I can't figure it out, I might go for the email gateway as well!

My problem is that my users have multiple carriers so I cannot specify just one. Realistically this all seems to go back to the problem that I had with it showing up as a nearly endless number of logs saying the data could not be unserialized because it expected a string and an array was given. I still have no idea when it would have been changed from a string to an array and I have not found an effect way to debug it. I still have only a very basic understanding of PHP and do not know how to go about truly understanding it enough to fix this. If anyone can help me out I would really appreciate it.

I'm on Bluehost with a Linux server.

The funny thing is when I try to dump the data it shows it as an Array which makes sense considering the way it was stored in the database. The part that is stored as a string is the gateway information which contains the carrier information as you can see below if you do the following
all of this is in the sms_user.module

  $result = db_query("SELECT number, status, code, gateway FROM {sms_user} WHERE uid = %d", $account->uid);

  $account->sms_user = array();
  while ($data = db_fetch_array($result)) {
-    $user_data = unserialize($data);
+    $user_data = $data;
    $account->sms_user = $user_data['sms_user'];
    $account->sms_user['number'] = $data['number'];
    $account->sms_user['status'] = $data['status'];
    $account->sms_user['code'] = $data['code'];
    $account->sms_user['gateway'] = unserialize($data['gateway']);
+  drupal_set_message(dprint_r($data, 1));
  }

if you print the data

Array
(
    [number] => 5555555555
    [status] => 2
    [code] => 
    [gateway] => a:1:{s:7:"carrier";s:23:"messaging.sprintpcs.com";}
)

if you try to print the gateway before you unserialize you will not get an output but if you print after you unserialize you will get

$account->sms_user['gateway'] = unserialize($data['gateway']);
drupal_set_message(dprint_r($account->sms_user['gateway'], 1));
(
    [carrier] => messaging.sprintpcs.com
)

so if you print just the carrier info from the gateway it will give you

drupal_set_message(dprint_r($account->sms_user['gateway']['carrier'], 1));
(
    [carrier] => messaging.sprintpcs.com
)

So I know the data is there I just don't know how to go about passing this information appropriately to the sms_email_gateway module

Messaging 6.x-4.x-dev (2011-Nov-11)
Notifications 6.x-4.x-dev (2011-Feb-26)
SMS Email Gateway 6.x-1.0
SMS Framework 6.x-2.0-alpha1

I think I might have figured out the problem but I need someone else to confirm this for me before I submit rebase the issue.

In messaging/messaging_sms/messaging_sms.module on line 59 change

  if (!empty($account->sms_user) && $account->sms_user[0]['status'] == 2 && !empty($account->sms_user[0]['number'])) {
-    return $account->sms_user[0]['number'];
  }

to 

  if (!empty($account->sms_user) && $account->sms_user[0]['status'] == 2 && !empty($account->sms_user[0]['number'])) {
+    if (!empty($account->sms_user[0]['gateway']['carrier'])) {
+      return $account->sms_user[0]['number'] .'@'. $account->sms_user[0]['gateway']['carrier'];
+    }
+    else {
+      return $account->sms_user[0]['number'];
+    }
  }

and then change sms_email_gateway/sms_email_gateway.module line 194 from

-  $to = $number .'@'. $options['carrier'];

to

+  if (!empty($options['carrier'])) {
+    $to = $number .'@'. $options['carrier'];
+  }
+  else {
+    $to = $number;
+  }

and I think it might work. The problem I'm assuming is that months ago when sms_email_gateway was split into a separate module they never bothered to update messaging_sms.module for the proper implementation. So when it passes the parameters it isn't doing it correctly. I'm also sure there is a better way to do this but I just want something that works for the time being until an expert can look at this.

I'm going to change this to the messaging framework because I think that is where the initial problem lies. Please let me know if this patch makes sense or if this should be in a different place because of the multiple modules using it.