Don't Back Down

Posted by Chad Everett on September 3, 2004

MT-Notifier 2.2.2 »

I've updated MT-Notifier to include a change that apparently was lost earlier.

There was a subscription method used outside of the management interface (introduced in MT-Notifier 2.2.0) that apparently was lost somewhere along the way, probably in the follow-up release that was supposed to correct other issues. This has now been fixed.

This change fixes the problem with stand-alone subscription forms not working, meaning that they should work correctly at this point. To my knowledge, everything else is working okay at this point, but keep those reports coming if you find anything is not working.

As is evidenced by this series of events, it's not out of the realm of possibility for me to screw something up (badly). Sorry for any difficulty this led to on your installations.

Announcement. Download.

Related Entries

Comments (12)

I get a problem when trying to click on the "Manage your subscriptions" link provided in the notifications emails. The system says: "You entered an incorrect address and/or code. Please correct the error and try again."

Can you provide the URL you are trying to access? Naturally, you may not want to post this publicly - feel free to email it to me directly.

Apologies in advance for what is surely a simple question: what templates exactly do I have to change in order to get a working checkbox that says "Check here to subscribe to this thread"?

Here's what I've done so far. I downloaded MT-notification v2.3, unzipped it, chmod'd and copied files according to mt-notification.txt. I ran the config CGI script, and installed the plugin onto the blog I'm interested in having notifications for.

I assumed this last step would change the checkbox automatically, because you say in the manual:

Because of limitations to the callback architecture in Movable Type 3.0D, an additional hack is necessary if you'd like to add a 'subscribe' checkbox to your comment forms, to allow posting and subscribing in one step. However, this process has been automated somewhat for you. Again using the Configure option, simply click the "install" link to make the necessary changes to your Comments.pm file. As of versoin 2.0.1, MT-Notifier is not compatible with MT-Blacklist. Forthcoming versions of MT-Blacklist should be compatible with MT 3.0D, and at such time, I will do everything I can to make them work together.

But it's not showing up for me. I rebuilt the website, restarted apache, posted a new test comment, rebuilt the website again, drank coffee and waited ten minutes (SOP to try this last thing, of course), repeated. No dice.

I then tried sticking the code someone cryptically placed on this page below where it says "Notes":


Check to Subscribe to this Comment:
LT sign input type="check" name="subscribe" GT sign

directly into some perlscripts and templates, and still no luck. Any help would be most appreciated. TIA for your help!
Best,
-j

Hi J - The code as you link it is correct, though "check" should be "checkbox", and it must be placed inside a form in order to work (though it may show up even if it isn't inside a form).

Specifically, this needs to go into the comment form - which in some cases may be generated by the MTCommentFields tag. If this latter case describes you, then the only way to do it at this time is to hack the module containing the MTCommentFields tag.

This will likely change in the future, but it's not otherwise possible at this time.

You may also accomplish the same task by using a template that does not make use of the MTCommentFields tag, so that you can add whatever you like to the form.

Okay, thanks. I'll try to hunt down the specific perlscript in which to put the HTML code. If I can get this working, I'll kick in some $ to your tip jar. Thanks again.

J, just a note - you don't need any perl, perlscript (?), java, javascript, php or anything else, if you are not using the MTCommentFields tag. This is a simple HTML form element.

If you do use the MTCommentFields tag, you will need to add some HTML into a Perl module, but it's not really Perl code (hope that makes sense).

If you need assistance, I do offer Movable Type Consulting through my company if you are interested. I'd be happy to take a look at this for you if you can't get it going on your own (there would be a small charge involved, depending on what exactly needed doing).

I installed Notifier on a site I'm developing. I built a generic subscribe form for the blog and tested it by inputting one of my own email addresses. Sure enough when I went into the Notifier manage panel I found my address subscribed. But I never got an email at my address confirming or asking me to confirm my subscription. Wasn't that a feature of Notifier? Where am I missing this in Notifier's settings? Thanks.

That is not a current feature of MT-Notifier. The next version is under development now, and may contain this feature. You can keep up with the current version at my Movable Type Solutions page. I'll announce any new versions there.

Chad, I have set Notifier to only send notifications on new entries. But today I got a flood of emails from Notifier. The only thing I did was to change the category assignment for my entries. Shouldn't that kind of operation be ignored by Notifier under this setting?

Hi Dave - This can be caused by a number of factors, but most importantly it happens because MT-Notifier requires that a record be written for an entry once a notification was sent. If the entry was written prior to the installation of MT-Notifier, then upon change (like this), that record will be written.

The other common occurence is that the process may time out if you have too many subscription records. I suspect this isn't the problem since you just installed it, but it could still be possible. To address this, make sure that you are using the most recent version, available at the Movable Type Solutions page.

I get a similar problem (I think). I have a emaillist too, that I put the posting email in the notify-address. When I post a blog entry that I have saved earlier as draft I get two-three notifications on the list instead of one. I have not tried to post directly without saving as dfraft yet.
I am not quite sure since I am not too good in english - am I to understand that this is due to the fact that I save as draft first, or is there a way to get around this so only one notification is made per entry?

Tomas, if you are getting multiple notifications, make sure you have the "update" option turned off. You will never get a notification if it's draft status - but during the save process, the entry is typically saved at least twice. If you are sending "updated" notifications, then you'll see this sort of behavior.

Leave a comment