Update: Latest Version = 1.1b
(now displayed at bottom of script's sidebar on left)
-------------------------------
The script below is a new way to allow readers to subscribe to yor comment posts. The original idea was from the ScriptyGoddess Subscribe-To-Comments scripts for MovableType. Jennifer, from ScriptyGoddess posted a call to any "doctor or Perl programmer in the house" because the Subscribe To Comments script is 1) a perfect opportunity for people to bombard enemies with spam emails, and 2) not helped by Jay Allen's masterwork the MT-Blacklist anti-spam plugin.
Well, as a better doctor than Perl programmer, I decided I'd better take up the challenge and have at it with my lumbering, kludgey Perl in order to sharpen my skills. So, I have hacked away at it for a few weeks in between real work, and I have produced a script which will easily substitute for the ScriptyGoddess one with very little work on your part and easy "revert" if you don't like it.
Here Are Some Features Of The Script
1) No hacking of MovableType or any related software
2) Single CGI script for easy installation and removal
3) Upgrade from ScriptyGoddess by simply changing two URLs in your Comments Listing Template
4) Easy Import of Old ScriptyGoddess Subscriptions
5) Web Based Interface For Managing All Subscriptions
6) Individual Entry Opt-Outs as Well as Sitewide Opt-Outs Available To Readers
7) Subscription Management Pages Secured By MovableType Password System
8) Subscriptions Stored In Database Instead of Flat File in Web Directory
9) Completely Compatible With Mt-Blacklist Plugin
10) Uses MT IP Banning For All Subscriptions
11) Readers Can Subscribe Without Posting, But Are Still Subject To MT IP Banning for Security
12) Completely Customizable Notification Email
13) Secure Reader Pages For Individuals To Manage Their Subscriptions
14) Reader and Blog Author Pages and All Others Separately Customizable With CSS
15) Easy to Purge All Related Data If Desired
16) Flood Control on Nonposting subscriptions
17) Optional automatic email notification if large volume of subscriptions (subscription spam warning)
18) Optional automatic (or reader chosen) expiration times for subscriptions
19) No hidden frames or occult popups - works perfectly* with both popup and inline comments
*the word "perfectly" is used largely to convey a feeling and not completely literally
. This is because, much as I love Macs, a couple of their
browsers are extremely inconsistent. The worst is Opera (Windows Opera is fine) - the workaround in the script causes a funny little bump that looks like the page is reloaded once
after posting a comment - no big deal, but might surprise those few Mac Opera users a little. Also, Safari puts up a dialog box saying "Subscription Info Processed Successfully" requiring a click on okay to get rid of it. Again, nothing too unusual, I hope. All other browsers behave themselves just fine.
If you want to try it out here first, subscribe to comments for this entry (with or without posting) and see how it works. You will receive an email that will give you a link to the reader's page (to manage your subscription(s) at this site).
See Sample Page From Script (Installation Instructions and Tech Notes)

Screenshot of Script's Subscription Page
Download Script -> EZ Subscribe To Comments
Change History
EZSTC 0.1b
add popup window to basic script
release for beta testing
EZSTC 0.2b
add ip banning
add popup toggle switch
EZSTC 0.3b - 0.9b
experimental frame designs
variable clearing
EZSTC 1.0b
web based interface
EZSTC 1.1b
devised non-popup method for hooking MT after comments eval'd
EZSTC 1.2b
Add full featured web-based interface
full entry-wide, site-wide opt outs
import from ScriptyGoddess
reader management page
css for user and reader interface
customizable email
subscribe without posting
release for further beta testing
EZSTC 1.3b
fix to allow for inline comments
EZSTC 1.4b
fix double posting in some browsers
EZSTC 1.5b
add timing loop to accomodate unconventional browser eval order
EZSTC 1.6b
fix for proper preview functioning
better variable checking
EZSTC 1.7b
further fixes for Mac Camino and Win Firebird
EZSTC 1.8b
add manage subscriptions by email address
EZSTC 1.85b
minor fixes for uninitialized variable warnings
EZSTC 1.86b
minor fixes for Opera compatibility
EZSTC 1.87b
allows for optional email address on comments form
EZSTC 1.09b
limited release test of new features
EZSTC 1.091b
add button to clone settings from one blog to another
EZSTC 1.092b
flood control not applied to nonposting UNsubscribe
EZSTC 1.1b
100% customizable email, per blog settings, add expiration dates, eliminate hidden frame, flood control
Comments
104 Responses to EZ Subscribe To CommentsTrackbacks
- : ActionScript Hero: EZ Subscribe To Comments Well, I'm going to install EZ subscribe to comments, a script to subscribe to comments developed by Oscar F Hills that it's not a hack. There are other scripts for subscribe to comments but you need to modify your Movable...
Tracked at 2004 01 13 06:12:34 - : 8 Ways to Sunday: EZ Subscribe To Comments I've added comment subscriptions to the blog, so you can follow the conversation on a given topic. Read on to learn the details...
Tracked at 2004 01 30 16:21:40 - : one girl's life: EZ Subscribe To Comments With many thanks to Oscar!...
Tracked at 2004 01 31 11:51:50 - : John's Jottings: EZ Subscribe To Comments Way too behind on maintaining this place, hoping it will get better soon. Some things in the pipeline: Upgrade to MT 2.661 Upgrade to MT-Blacklist v1.63 beta Upgrade to MT-Textile 2.0 Upgrade to PHP 4.3.4 Upgrade to phpMyAdmin 2.5.5.pl1 Upgrade to Apac...
Tracked at 2004 02 06 05:59:20 - : jasonheyd.: EZ Subscribe To Comments installed the EZ Subscribe to Comments plugin recently. so, now you can track replies to comments, should you so desire....
Tracked at 2004 02 17 11:35:42 - : Al-Muhajabah's Movable Type Tips: EZ Subscribe To Comments The blog author gets an email notification whenever a new comment is posted on their blog. But, often, commentors themselves would like to be notified when new comments are posted to entries that they're monitoring. The venerable solution is the...
Tracked at 2004 02 17 18:34:30 - : A Soft Answer: EZ Subscribe To Comments Well I was going to delete this post after I used it for a test, but Hugh pegged it with a comment. So it wouldn't be fair to delete the post but I thought I would at least post what I am trying to do behind the scenes in case anyone else with Movable ...
Tracked at 2004 03 19 11:07:59 - : A Soft Answer: EZ Subscribe To Comments Well I was going to delete this post after I used it for a test, but Hugh pegged it with a comment. So it wouldn't be fair to delete the post but I thought I would at least post what I am trying to do behind the scenes in case anyone else with Movable ...
Tracked at 2004 03 19 11:08:17 - : 8 Ways to Sunday: EZ Subscribe To Comments I just upgraded this blog to Movable Type 3.0 beta 2. Curious about the new version? Here are some of the highlights...
Tracked at 2004 05 06 11:35:23
Tell us your thoughts...
And (as you probably know) if you want a pic to show with your comment, go get a gravatar!
Next entry: Jerry Reed's Drive In
Previous entry: NetFlix Suite
EZ Subscribe To Comments
Posted by Oscar on Tue, 11/18/03 at 07:44 PM
Filed under: •
MT & Web Design •
Comments: 104 Comments/Trackbacks

OFH Solo Banjo/Guitar mp3's
pretty good if you like pickin'























































April 18th, 2004 at 06:30 pm
Thanks Justin. Yes, people often don’t know about that line. Very important for inline!
April 18th, 2004 at 05:51 pm
Oscar- I just had a problem with my comment-posting code in my individual archives (I use inline comments) that I thought would be helpful to share.
My “remember me” feature was not working (unrelated to EZSTC), and in the process of fixing it, I inadvertently deleted this line of code:
<input type=“hidden” name=“static” value=“1” />
from this section of my template:
<div class=“comments-body”>
<form method=“post” action=”<$MTCGIPath$><$MTCommentScript$>” name=“comments_form” onsubmit=“if (this.bakecookie[0].checked) rememberMe(this)”>
<input type=“hidden” name=“static” value=“1” />
<input type=“hidden” name=“entry_id” value=”<$MTEntryID$>” />
This omission makes MT take the user to the MT comment script after they post a comment, which isn’t good if you aren’t using popup comments. I assume the “static” part means one is using inline comments rather than viewing from “mt-comments.cgi?entry_id=xxx”.
Like I said, it really has nothing to do with EZSTC other than that I could just as easily have deleted that crucial line when installing EZSTC. Also, people like me may blame your script when this is the error. Thanks for the great script.
Oh, and ShoutBox spam seems to be growing…
April 6th, 2004 at 10:09 am
Hello!
I installed your great plug-in. It works just fine with English Posts.
But I sometimes use Japanese, which contains 2 byte characters. When I use Japanese in comment, the letters are destroyed. I think I need to set CHARSET to UTF-8 and I tried hard to find where in the code to modify, but never succeed.
Would you please give me some hint?
Thank you very much in advance.
March 8th, 2004 at 11:38 am
Hi Paul - I DID get your email. Sorry to be long in responding, but I have been overloaded with non-computer work. I willm take a look as soon as I can ...
March 8th, 2004 at 08:41 am
Hi Oscar,
I sent you an email a few days ago about my problems…
I don t know if you had time to look at him but my server went down for a few hours this We and some mails might have been lost… please let me know.
Thank you for your time and help. and devotion.
February 19th, 2004 at 05:19 pm
Thanks Justin. The test script I sent just cleaned up a few things, but I have no idea whether any of that is really necessary. So far, the folks who have had trouble have solved it by hunting down other problems on their servers. I am working on a few other things related to the script, so I won’t bother with another release at the moment unless someone finds that the current script doesn’t work for them. Thanks again for the update.
February 19th, 2004 at 01:01 pm
To answer your question - I’m not sure which part wasn’t working. It may just have been the MT template/form tags. At any rate, subscriptions are working. Thanks!
February 19th, 2004 at 12:29 pm
After I installed the script you emailed me, I still couldn’t get it to work. When I uploaded the plugindata module, it started working. I had also had a few issues with closing the tags in the wrong place, but this was easier to fix because I could just copy and paste from a site that worked (in this case, MT-Plugins, since I like their layout and use the same features). It works great now.
I hope this experience is useful to others. To summarize what I did (not in order, but what ideally would have been the order):
1. I had my webhost install the storable.pm module, which they did within ten minutes, since it wasn’t already on the server.
2. I installed the plugindata.pm module in cgi-bin/extlib/MT/plugins. CHMOD to 755. (not sure if this is necessary)
3. I added the EZ Subscribe to Comments plugin file to my main MT directory (the cgi-bin). CHMOD to 755.
4. I modified my templates to include the necessary subscription forms (by copying the HTML from pages like this one that work).
5. I tested it with my email account.
February 19th, 2004 at 06:18 am
Justin - Which thing worked? The plugindata module or the test script I sent you?
February 19th, 2004 at 03:07 am
Ah, yes. That works. Thanks for your help and excellent plugin!
February 19th, 2004 at 02:36 am
I’m still trying to get it to work…I think I have Plugindata in the wrong place or not installed. Where does it go? I found a copy of it somewhere, and put it in /extlib/MT/plugins. Is this where it goes?
Thanks!
February 18th, 2004 at 07:20 pm
Thanks for writing this great script. It’s running, and I have all the modules installed on my server, but I’m not getting the emails when I try a test subscription on my site. So I thought I’d do a post here after subscribing and see if it works. Thanks!
February 13th, 2004 at 09:45 pm
You have all the modules you need on your linux server.
If you are getting a “Premature end of script headers” each time you post a comment to an entry that has a subscription, then there is either a server side problem or some bad data in the comment listing template being passed. I just can’t get the script to produce an error here (not to say that there might not be a bug somewhere).
Do you have a link to the test blog I could take a quick look at? Otherwise, I’m just not sure what the problem is ... no one else has reproted it (yet!) ...
February 13th, 2004 at 09:21 pm
I do get the comment emails from MT (including the handy link back to MT-Blacklist). So, MT doesn’t have any issue sending mail. There are no other required perl modules or anything?
February 13th, 2004 at 02:09 pm
Hmmm ... it doesn’t throw any errors on either of my two servers, so I’m not sure what the problem might be. Do you get regular notification emails of posted comments yourself? Are you possibly not hooked into your emailer? This uses MT’s Perl email hook.
February 12th, 2004 at 10:33 pm
Yes, the script’s info page does come up, and my test subscriptions are even saved. I had actually already changed some settings (most specifically the sending email address). So, it would appear that the database is set up OK.
I’m using Mozilla 1.5 and haven’t tried any other browser with it at this point. The symptoms seem to point to a server-side issue, anyhow.
Unfortunately, I don’t have much access to poke around on my server. I could try adding some logging statements to the script sometime to see if I can track down the problem. I figured I’d see if you had heard of anything similar before I went down that route…
February 12th, 2004 at 10:17 pm
Hi Kevin - No, it should work. Try these two things - first point your browser to the script. Does the script’s Info page come up? (I assume so, since you got to the instructions). If so, go to the configuration page and select the blog, then click “Save” for any one of the sections. That should establish the database (it should work without this, but ...).
Then try a test again. Also, what browser are you using? Does it work with a different one? Any info you have will help me track down the problem.
Also, did you subscribe to a test post? Does the subscription show up in the management page?
February 12th, 2004 at 10:04 pm
Hi, Oscar
This looks like a great script! I’ve set it up on my test blog, and the comments are posted to the site just fine, but I haven’t received any email messages. I have MT-Blacklist installed, so I should have all of the pre-reqs met. Other than cosmetic changes, I’ve pulled the forms straight out of the instructions.
I just looked at my server error log, and it is showing the rather unhelpful message “Premature end of script headers”. This despite the fact that I am forwarded on to the comment listing page.
Is there anything else I need to have installed for sending to work properly?
Thanks!
February 11th, 2004 at 10:46 am
Hi Kristine - Yes, I saw that link at the Directory, and was reminded of that function in the ScriptyGoddess version. The short answer is that a link is sent with every notification e-mail (at least that’s the default - blog owners can elect not to include it). When users click on the link, which includes a 10 character code unique to their subscription to that entry, they are brought to a page where they can manage all their subscriptions, i.e., change the duration, unsubscribe, opt-out of an entry, or opt out of the whole site.
If they unsubscribe to the entry that brought them to the page, they can only get back to the page by following the link and code from another one of their subscriptions - since the code for that one is now gone. But, they can choose all the actions they want first, and then click “Update” on the user page.
Heh, that was the short answer. The long answer is:
When Jennifer at ScriptyGoddess first solicited contributions to the “subscribe to comments” problem, she was particularly interested in comment and subscription security. In the original version, I think the worst malice a person could wreak on the “Manage Your Subscriptions” page would have been to sign in with someone else’s email address and delete all their subscriptions (not likely really). Now, they would be able to add an entry-wide or site-wide opt out as well. It just seemed better to ensure that only the person actually receiving the notification email would be given access to their “manage” page - hence the code. But, once there, they can manage ALL their subscriptions at once.
I am open to suggestions. It would be easy to allow a link where people could just use the email address without the code. I could include that as an option in the configuration page, but it seems a little too “unsecure” for these times. But I will respoind to what folks want in the script.
February 11th, 2004 at 01:26 am
Oscar, on the ScriptyGoddess script, there was a way to add a “manage subscriptions” link right in the Individual Archive for the entry. (the plugin directory still has this link, even though it doesn’t work, because I haven’t had a chance to figure this out until now
) Now I see that when I make a comment, it tells me where to go to manage my subscription, but is there a generic URL that can be used for USERS to see all their subscriptions in one place?
Under “Reader Interface Page”, it sounds like there isn’t, but I figured it couldn’t hurt to ask.
Thanks!
Page 2 of 5 pages < 1 2 3 4 > Last »