Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Notify
This discussion has been closed.
Comments
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
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??
Posted: Sunday, 13 January 2008 at 8:32AM
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.
There is also a little Bug in default.php on line 153. You hardcoded "LUM_User" there.
PS:
Notify seems to conflict with the LowCal Plugin. When LowCal the subscription link stops working.
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...
today I tried to translate "Notify" and some other Add-ons, too, into German and noticed most of them use the "old style" for declaring the language variables.
So I made a convertion (with the help of "sed" described here) to use the documented "new style" for the "Notify" extension.
If you want (an I recommend it) you can download the patch or/and the new "default.php" from my site at http://sokai.name/code/vanilla/add-ons/.
For all German people: The translated text can be downloaded from http://sokai.name/code/vanilla/translation/.
Thanks a lot,
sokai
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
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.