Error when signing up for Mobile alerts

[Nhorning]

Fatal error: Using $this when not in object context in /home/nepalmon/public_html/application/helpers/alert.php on line 34

When using the Alerts page to sign up for mobile alerts. Any advice?

[rjmackay]

That doesn't look good. Can you add more information on how to reproduce this bug and what version of the software you were using?
https://wiki.ushahidi.com/display/WIKI/Report+a+bug

[rjmackay]

Also - in this case its probably relevant to add what plugins you're using (especially for sending/receiving SMS)

[Nhorning]

Right, sorry about that. Would you believe I used to be a software tester....

Ushahidi 2.5 But I had a very strange upgrade where I had to do a fresh install without using the installer, and manually create auth.php, config.php, and encryption.php

I believe this is happening in both Firefox and Chrome. I'm working from Ubuntu 11.10 so I don't know if it's happening in IE

To reporduce:

• Enable Signing up for Mobile Alerts by Making sure Display Mobile Option is set to "True" in /Controllers/Alerts.php
• Make sure SMS sync is selected as the SMS provider in Settings>SMS in the Ushahidi interface.
• Navigate to the alerts page and attempt to sign up for an alert as a test.
• Fatal error: Using $this when not in object context in /home/nepalmon/public_html/application/helpers/alert.php on line 34 will display on a white screen.

Note: manually modifying e-mail alert recipients in the database to be SMS alert recipients does not seem to result in Alerts being sent either. However, I don't think whether SMS alerts work can be properly tested on my deployment until this issue is resolved.

Installed plugins:

Add This: 0.1
Admin Map (High Performance) 2.0
Facebook Social 0.6 (slightly modified with a submitted pull request)
FrontlineSMS 0.5
Location Highlighter - Lite 1.0
SMSSync 0.8

Uninstalled but listed Plugins:

Clickatell 0.5
Enhanced Map 2.1
Heatmap 0.8
Ushahidi API Library 1.0
Sharing 0.1
Sharing 2.0
Time Span 1.1
Viddler 0.1

[rjmackay]

Look at the code its actually a fairly simple and obvious error. Still present in 2.6 sadly so you might need to patch manually.

[Nhorning]

Yes, That would have been simple and obvious if I knew PHP. A few days ago when I started looking into this, I pretty much knew it was an error with that line, but had no idea what to do with it. I'll patch manually and see if this works. Next will be to see if the alerts actually go out. Thanks a bunch for this!