MT-Notifier 2.4.6 »
I'm releasing MT-Notifier version 2.4.6 today.
This adds a couple of changes.
2.4.4 - Added MTNotifierCatID template tag to display ID of context category.
This change allows you to use the MTNotifierCatID tag inside of a context category - useful for pulling out the category ID when you are in a category archive, for instance, and allowing you to dynamically create subscriptions for categories.
2.4.5 - Added ability to specify parameter "url" on subscription form.
If you create your own subscription form, add the parameter "url" to the form. You can make this hidden, and I would probably suggest doing so, but you could also allow it to be a drop-down list or something. Regardless, when the parameter is included in a subscription form, this will re-route the subscriber to the page specified. You should not include a query string in this parameter - or if you do, encode it (though it still may not work).
2.4.6 - Fixed regex for handling single-digit subscriptions.
David, plugin author extraordinaire, pointed out a problem in one of my regular expressions. If you were having problems subscribing to single-digit entry IDs, this could be the case. Thanks for finding this, David!
At the same time, I also updated the category and blog regular expressions to handle those numbers more accurately.
Comments (15)
Would you mind adding the statement that mt-notify isn't compatible with mt-blacklist in the paragraph above the installation notes?
The fault can be placed on me for not reading the entire readme but if that were pointed out before, it would have been quite a bit less stressful. I swear I had almost gone through every MT related file looking for reasons why it wouldn't show up.
..and then I read mt-notifier.txt completely. ;D
Posted by t3ase on March 11, 2005 2:49 AM
Sure, I'll move it for a future release. But I'm not so sure it's completely "not compatible". I have heard of a number of people that say that it works. I don't specifically use that configuration, so I can't say... but there may be other factors at work, too.
Posted by Chad Everett on March 11, 2005 1:57 PM
Hmmm, maybe some google time may yield a hack or two. I'll check in to it and if I find easy directions, I may give ya the link for future release info.
Thanks.
Posted by t3ase on March 12, 2005 12:33 AM
What a great plugin :) I looked at it initially because there's a bug in MT3.15 that means my notify isn't working but I'm delighted to find that people can subscribe to categories :) Thank you, it's just what I needed.
Posted by Shelagh on March 12, 2005 8:07 AM
FYI, I'm having success with latest MT-Notifier playing nicely with MT-Blacklist 2.04b. (so far, so good!) Thanks for this helpful plugin.
Posted by kate on March 12, 2005 8:21 AM
RE: Shelagh's comment - Does MT-notifier solve the blog update notification bug in MT 3.15? I had understood that it would not. I get the update notices, but my readers do not. Read more about it here.
Posted by salguod on March 16, 2005 9:51 AM
Hi. I had previously installed Notifier 1.4.1 and have now upgraded it to the latest version 2.4.6. in the hopes of getting email notifications going again given the bug in MT 3.15. I haven't found any detailed documentation on the transfer function. On IE 6 Win XP, I'm not able to type anything into the box for the path for the file to be transfered into MT-Notifier. Other operations seem to be working just fine. If the transfer malfunction is just an issue with my work station, would the path to the old Movable Type Notifications (for transfer) be the path to the page where you view the notifications list from within MT? Thanks in advance for further tips on transfers.
Posted by stacey on March 16, 2005 3:20 PM
The path isn't used for MT-Notifier v1.x transfers. Only for Scripty Goddess transfers.
Posted by Chad Everett on March 16, 2005 4:19 PM
I recently installed Notifier and it worked fine with a couple of test email addresses subscribe. However, will the full 100+ email addresses subscribed nothing gets sent out. Paths to sendmail are right - is there something in the configuration of Notifier that I have got wrong?
thanks
Posted by Ed on March 20, 2005 6:08 PM
Weirdly - Notififier *was* working fine for me until two weeks ago - dishout comment notifications, without any problem.
Now, on two completely unrelated websites, it's stopped working - the emails just don't arrived.
Completely baffled...
any ideas?
d
Posted by dave on March 23, 2005 5:36 AM
MT 3.14 + MT-Blacklist 2.04b + MT-Notifier 2.46
In testing mode - everything seems to work - _EXCEPT_ the comment form "hack" cited in mt-notifier.txt to add the subscribe check box....
I see the code that was added to Comments.pm:
if ($q->param('subscribe')) { # jayseae::notifier
require jayseae::notifier; # jayseae::notifier
jayseae::notifier->subscribe($comment); # jayseae::notifier
} # jayseae::notifier
But the check box does not show up...
Why?
Thanks,
fletch@med.stanford.edu
Posted by fletch on March 23, 2005 1:11 PM
Because that doesn't add the checkbox. That code processes the checkbox. You need to add the checkbox to your form manually.
Posted by Chad Everett on March 24, 2005 7:56 AM
This indeed is a great plugin. Everything works except email does not always get sent. I suspect I am setting things up in the wrong order?
Has anyone else run this with MT 3.15 yet? ( thats what I have)
I notice the in the documentation should now be replaced with per the 2.4.4 fix.
Ian
Posted by Ian Wells on March 25, 2005 6:53 PM
Hi Chad,
Does MTNotifier work when an entry is posted via XMLRPC? I can get notifications sent when posting through MT's web interface, but not when entries are posted via the XML-RPC interface.
Thanks,
Francois.
Posted by padawan on May 14, 2005 12:36 PM
Francois, I have no idea. My instinct would be to say that it does, as it's a callback on the save process of the object. But it's also quite possible that posting via XML-RPC does not call the save in the same way, which would mean that it does not.
Posted by Chad Everett on May 14, 2005 4:49 PM