small bug in default.php (around line 429)

it causes trying to add script tags where it is not needed
and it causes to break ajax if enabled extensions during ajax call (check last lines of appg/init_ajax.php) and therefore it is not possible to disable any extension then - it displays alert with error message about $Head not defined because it is not defined in init_ajax and it doesn't uninstall the extension

this: if (in_array($Context->SelfUrl, array('comments.php','index.php','account.php','categories.php')))
$Head->AddScript('js/prototype.js');
$Head->AddScript('js/scriptaculous.js');
$Head->AddScript('extensions/Notify/functions.js');should beif (in_array($Context->SelfUrl, array('comments.php','index.php','account.php','categories.php'))) {
$Head->AddScript('js/prototype.js');
$Head->AddScript('js/scriptaculous.js');
$Head->AddScript('extensions/Notify/functions.js');
}

ah! sorry :) next time I should update to the latest version first :)

Download the latest version.

Minisweeper: I use Notify 1.2.1 (downloaded today) with Vanilla 1.1.4 and now the problem seems to be given only by Safari 1. Thanks

Is it just me, or do {user}, {title} and {comment} not equal anything in email_notify.txt?

Also, {topic_url} refers to an "ugly" permalink, rather than the "pretty" mod_rewrite permalinks I have set up. Any ideas?

If I can get all the code worked out, I may be able to continue some development on this.

I have this problem either. I guess it is something with order or loading prototype.js and scriptaculous.js
Just have had no time to find the cause

I have the latest version of notify installed and believe my smtp, user and pass settings are correct.

I am getting the following error whenever I add to a discussion.

Any help would be greatly appreciated.

Notice: Undefined variable: mComment in /home/content/g/s/1/gs1991999/html/vanilla/extensions/Notify/default.php on line 309

Notice: Undefined variable: mUser in /home/content/g/s/1/gs1991999/html/vanilla/extensions/Notify/default.php on line 309

Warning: fsockopen(): unable to connect to smtp.gmail.com:587 in /home/content/g/s/1/gs1991999/html/vanilla/library/Framework/Framework.Class.Email.php on line 196
A fatal, non-recoverable error has occurred
Technical information (for support personel):

Error Message
Could not connect to SMTP host smtp.gmail.com:587
Affected Elements
Email.SMTPSend();

The error occurred on or near: 110: Connection timed out

I seem to be one of the lucky ones that have Notify working correctly.

My question is: where does X-Mailer: Lussumo Mailer in the header of the received email come from?

I have searched all the associated files but it's not there, I even checked the language file.

Posted: Friday, 28 December 2007 at 9:37AM

Great extension by the way.

However I just installed this for the first time and I'm getting a similar error to above:

Notice: Undefined variable: mComment in /public_html/extensions/Notify/default.php on line 309, referer: http://xxxxx.com/post/474/
Notice: Undefined variable: mUser in /public_html/extensions/Notify/default.php on line 309, referer: http://xxxxx.com/post/474/


I don't see either of those variables anywhere else in the add-on, except for line 309. So, I'm thinking that the error is true.

Any ideas??

I'm having an odd issue. I've installed and tweaked a good 20 other add-ons, but can't even get this add-on to register in the extensions menu, therefore can't enable it. I'm tempted to add the code into the include file myself, but it seems odd that It doesn't come up?

Sorry to add a third post....

It's working a charm with my install. However...

1 - When you tick/untick a notification setting on the account page, it does the AJAX doo-da and works, but leaves you with a blank line rather than a ticked/unticked box.

2 - Forcing e-mail notification on, would be lovely, if people also had the option to force it off. Or, perhaps make it default that whenever you post a new discussion, you automatically subscribe.

does notify work with 'user wall' ?

I am experiencing the same problem that a few people have mentioned in this thread - when you click one of the subscribe/unsubscribe links, the three green 'AJAX' loading dots appear infinitely, and the change is never applied.

As above, disabling LowCal seems to fix the problem so there is obviously a conflict here.

I have also found that this extension conflicts with Comment Links - it disables the JS drop down.

Any idea what can be done? I've informed each of the extensions of the conflicts they are having...

Joey,

How did you do the following? I'm having the same problems with JQMedia. I'm still not 100% comfortable with the Vanilla scripting/extension language, so any help with this would be loved.

"It did not interact well with JQMedia on my configuration. I now eventually have alot of the features working after disabling JQuery v12-1.1.4 and all other JQ extensions temporarily to enable the Notify extension first then I re-enabled the JQuery v12-1.1.4 and other JQ extensions afterward. I had to modify the default.php for JQmedia 0.5.1 to have JQmedia included in all the pages that had Notify panel links, not just the comments.php and posts.php pages (as is where JQmedia appears to be included by default). For some reason JQmedia and some other JQuery extensions had a bad effect on the Notify extension's javascript includes in the header when displayed in certain various orders even when notify was enabled first through the settings extension control panel. The quickest way I discovered to fix the JQmedia conflict in my configuration was to either disable JQmedia or, as I stated above, just simply included JQmedia on all pages containing the Notify extension "subscribe" and "unsubscribe" links."

mcs

if there r to be updates for this
can the updates include notify working for comments on the user wall?
that would be awesome
^_^

I always wanted to get rid of the prototype/scriptaculous dependence (for me only occuring when using Notify) of the non-administrative Vanilla frontend to increase speed a little. So I replaced the scriptaculous calls with Vanilla-native ones and added some functionality. See the script here. It is only compatible with Browsers supporting w3c-dom functions!!

edit- oops forgot to say that if you want to use it, it makes sense to remove the injection of prototype and scriptaculous at the end of default.php

change:
$Head->AddScript('js/prototype.js');
$Head->AddScript('js/scriptaculous.js');
to:
//$Head->AddScript('js/prototype.js');
//$Head->AddScript('js/scriptaculous.js');
or just remove it.

Does Notify have any known security issues? I'm getting spam sent to me, and it appears to be coming from a script on my server. I have very few on this server that could be doing it, so I'm wondering about Notify, especially as they all contain "comment3" or "comment4" as a keyword.

Use $Context->Dictionary in extension's default.php is poor coding. Use $Context->SetDefinition

With the latest install it appears that the default setting for notify has no checks to receive emails for any new or existing threads or comments. Can someone please advise me on this?
Thanks!

I get there was a problem authenticating your post information. when trying to enable the plugin. Any suggestions?

Notice the followings errors in my error_log today, any idea as to why this would be happening?
[22-Jun-2008 22:03:31] PHP Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/XXXX/public_html/live/public/forums/extensions/Notify/default.php on line 252
[22-Jun-2008 22:03:31] PHP Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/XXXX/public_html/live/public/forums/extensions/Notify/default.php on line 264
[22-Jun-2008 22:03:31] PHP Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/XXXX/public_html/live/public/forums/extensions/Notify/default.php on line 273

After installing this extension on my Wordpress integrated Vanilla, I found that it didn't work. So I went bug hunting. I changed the hardcoded table and column names to use $Context->DatabaseTables/Columns, and fixed some other little bugs. It now works in my - admittedly very vanilla - install of Vanilla. I figured I'd give everyone else the opportunity to use my patched version.

Notify 1.2.2 - CHANGES

default.php:
-changed some of the default strings
-changed the User table references to $Context->DatabaseTables['User']
-changed references to columns in the User table to $Context->DatabaseColumns['User']['ColumnName'] (hope I got 'em all; note: the Notify table and columns are still hardcoded)
-fixed a label in the Notify config page; the label for "entire forum" was broken

functions.js
-removed duplicate "$(Elem).innerHTML = NewText;" that was unconditional - this was causing config settings to vanish from the config page on click

-removed Mac folder from base directory
-changed permissions on Notify folder to 755; it was 750 which was causing the extension not to show up on the extensions page

If there is interest and the original author gives his permission, I might be willing to maintain this extension and add any further features to it.

Just responding to my own post above, following Joey's method in page3 worked, but I used this line to make it work.
$e->Subject = $DiscussionForm->Context->Configuration['APPLICATION_TITLE'].' "'.$mTitle.'" ';
Joey's was $e->Subject = $DiscussionForm->Context->Configuration[''APPLICATION_TITLE''].' "'.$mTitle.'" ';

Can anyone tell me how I can display forum names instead of {name}? {name} displays whatever is in "Name" field. But I would liek to display forum names.

Thanks.

thanks tty.

Question: If the user is logged in the Notify extension works as expected, and sends an email to them with link to discussion topic. However, if user is not authenticated, the page they go to says "discussion not found," and to a casual user looks like an error message. Is there a way for the link in the email (or script) to ask user to login first, then redirect to the specific discussion they're subscribed afterwards?

Thanks.