Plugin: SageAlert v2.x

[Slugger]

Originally Posted by razrsharpe

any chance we could have a general CSV server property that specifies the folder for where all the CSV logs end up?

Add a feature request ticket and I can probably add it at some point, but as I explain in the post a couple before this one, feature requests are currently on the back burner. Also, as mentioned above, I'm definitely willing to accept a patch and can easily apply and build a new version for the Sage plugin repository.

[Deacon Crusher]

Trying to use gmail or comcast.net.

gmail wants a TLS connection, will the SSL checkbox provide that?

Comcast.net wants to use the smtp submission port 587.

can I do a server address

smtp.comcast.net:587

Just adding my vote to create a test the settings button.

Thanks for the great utility.

[Slugger]

Originally Posted by Deacon Crusher

Trying to use gmail or comcast.net.

gmail wants a TLS connection, will the SSL checkbox provide that?

Yes.

Comcast.net wants to use the smtp submission port 587.

can I do a server address

smtp.comcast.net:587

Just enter the host name and then use 587 in the port field.

Just adding my vote to create a test the settings button.

Thanks for the great utility.

Forgot about this. Best bet is to always open an issue ticket at the project site. Most of my project work is pulled from tickets on there. Messages/emails/IMs/PMs get lost/deleted/forgotten, issue tickets are visible until I close them.

[razrsharpe]

Originally Posted by Slugger

Just enter the host name and then use 587 in the port field.

i had leave the port as -1 for it to work for me (using smtp.comcast.net)... wouldn't work otherwise

[Slugger]

Originally Posted by razrsharpe

i had leave the port as -1 for it to work for me (using smtp.comcast.net)... wouldn't work otherwise

-1 tells the javax.mail api to use the default port for the service. In the case of SMTP, that's port 25 so if using -1 for smtp.comcast.net works then it's actually using port 25 (so changing the setting to 25 in SageAlert would also work).

[darcilicious]

There was a software update message for "Phoenix Core Services" so I installed that and restart SageTV.

After the restart, there were two new System Messages:

1) Software Update for SageAlert to version 2.0.0.920
2) Then a General System message:

SageAlert: Licensse file is invalid or not found; some features of this software have been disabled.
SMTP server support disabled.
Only one notification sent per event.
Please consider making a donation.

When I select the Software Update message, I get the following pop-up message:

"No update options are currently available for this plugin because the plugin has already been updated."

But I hadn't updated it yet or anything, just restarted SageTV service per the Phoenix Core Services update.

Just thought I'd let you know...

[Slugger]

That's weird... sounds like an issue with the Plugin Manager. I definitely do not force an upgrade of SageAlert in any way - ever.

EDIT: Typo in error message corrected for next build, thanks.

[darcilicious]

Sigh. I think it was operator error or something in the plugin screen / system messages screen and I may have unintentionally upgraded the wrong thing.

As much as I like the idea of SageAlert, twitter has just been so unreliable

[GKusnick]

Originally Posted by darcilicious

As much as I like the idea of SageAlert, twitter has just been so unreliable

You don't need Twitter to get SageAlert messages on your phone. Your phone carrier almost certainly has an SMS gateway that can receive email alerts addressed to yourcellnumber@yourcarrier.com (or something along those lines) and forward them as text messages to your phone. See this list for details about your carrier.

[darcilicious]

Yes, that's another option I'm considering

[matterw]

Originally Posted by darcilicious

There was a software update message for "Phoenix Core Services" so I installed that and restart SageTV.

After the restart, there were two new System Messages:

1) Software Update for SageAlert to version 2.0.0.920
2) Then a General System message:

SageAlert: Licensse file is invalid or not found; some features of this software have been disabled.
SMTP server support disabled.
Only one notification sent per event.
Please consider making a donation.

When I select the Software Update message, I get the following pop-up message:

"No update options are currently available for this plugin because the plugin has already been updated."

But I hadn't updated it yet or anything, just restarted SageTV service per the Phoenix Core Services update.

Just thought I'd let you know...

Same exact message on my setup too. Any ideas?

[Slugger]

I assume you upgraded SageAlert? The message is simply telling you that some features of the plugin have been disabled. If SageAlert was upgraded without you doing it then that's an unknown issue with the plugin manager that you'll want to take up with Sage support. I promise everyone I am not forcing an upgrade of SageAlert - or any of my plugins.

[kmp14]

Ok, dumb question time. How do make a donation/get a license file? I dont want to upgrade until I have the license file.

[Slugger]

Originally Posted by kmp14

Ok, dumb question time. How do make a donation/get a license file? I dont want to upgrade until I have the license file.

There is a donate button on the web GUI after you upgrade. You have to upgrade to get the button. If you donate before I go to bed then you won't have to wait long to get the license file, otherwise, I'll process it in the morning.

[wayner]

Hi Slugger - I don't mind donating since I use several of your plugins but before I choose the amount I would like to know if you will be implementing a similar donation policy with your other Sage plugins?

Nevermind - after clicking on donation I see that you hardcoded the amount into Paypal.

[Slugger]

Originally Posted by wayner

Hi Slugger - I don't mind donating since I use several of your plugins but before I choose the amount I would like to know if you will be implementing a similar donation policy with your other Sage plugins?

Nevermind - after clicking on donation I see that you hardcoded the amount into Paypal.

I think I've answered most of the popular questions here.

[toricred]

There's one question I don't see answered, but I may have missed it. If you start charging for other plugins will donators have to pay for each separately? I'm not at all begrudging the donation. I just want to understand the parameters.

[Slugger]

Originally Posted by toricred

There's one question I don't see answered, but I may have missed it. If you start charging for other plugins will donators have to pay for each separately? I'm not at all begrudging the donation. I just want to understand the parameters.

FAQ updated:

Will a license for one plugin be valid for all the others requiring a license?

I have not made a decision on this yet. I'll decide once I add licensing to a second project. I'm leaning towards "yes", but I haven't decided yet.

[Slugger]

The latest snapshot of SageAlert (935) requires a new license file. Current donators will be receiving replacement license files by Sunday evening and may wish to wait until receiving your new license before upgrading. I don't anticipate any changes requiring replacement licenses in the near future after this upgrade.

[Slugger]

All replacement licenses have been issued. These new licenses are only good for SageAlert v2.0.0.935+. If you did not receive yours, please let me know. As I said earlier, I don't expect to have to reissue new license files any time soon. It certainly will not be necessary for each new build to apply a new license.