Okay, here is the packaged up version of ComeBack for Movable Type.
- Download cb-mt.tar.gz or cb-mt.zip
- Unpack the archive and place:
- ComeBack.pm in your lib/MT/App/ directory
- ConfigMgr.pm in your lib/MT/ directory
- cb_url.pl in your plugins/ directory
- mt-cb.cgi in your base MT directory
- Add the following line to your mt.cfg file if you have to rename mt-cb.cgi to something else (e.g mt-cb.pl):
ComeBackScript mt-cb.pl
The plugin part adds the following tags to MT: MTComeBackScript and MTEntryComeBackLink. You can use them just like their Trackback cousins.
I also implemented an example ComeBack pinging script. You can download send-cb.tar.gz or send-cb.zip. In there are two files, send-cb.pl and XML/ComeBack.pm (which is basically a hacked-up version of Tim's XML::TrackBack perl module.
Play around with them and see what happens.
Update: Fixed a couple bugs. Download the new archive.
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
Help! I have a problem!
When I add the line to my mt.cfg file, I get the following error when I try to log in:
"Got an error: ./mt.cfg:187: variable 'ComeBackScript' not defined"
Any ideas? I followed your instructions exactly and have uploaded all files using ASCII. Commenting out that line lets me in but I imagine it will also deactivate the ComeBack mechanism.
D'oh! My apologies. I put that up last night, and I had to get to bed pretty early, so I hadn't fully tested it yet. Just grab the latest archive, which contains a patched version of ConfigMgr.pm for MT. That should work fine.
Posted Via: send-cb.pl (Version 0.1)
Works great now, thanks :).
Okay, I'm still pretty fuzzy about how ComeBack works. Do both parties have to have ComeBack installed? If I was to enable it on the plugin directory, and you were to ping the directory when you added a plugin, then people could leave a comment for YOU over there and it would show up both on the plugin comments page AND in your thread that you pinged from? Hmmm.....
will this comment show up elsewhere?
i'm testing it on my blog, the comments are sent, and i receive notification but the script returns a 500 error when i use the version i downloaded.
i figured i needed to send a content header so i tried this:
print "Content-Type: text/html\n\n";
and text/xml ... when i try that, i dont get a 500 server error but i do get an xml error in the top of the page, when i veiw the source i get this:
Received: <?xml version="1.0" encoding="iso-8859-1"?>
<response>
<error>0</error>
</response>
and in the page it get this:
Received: 0 Woo hoo! Ping to http://www.dotfaf.com/cgi-bin/mt/mt-cb.cgi/754 sent successfully
++++
Any thoughts? Or is that how it's supposed to work? i'd rather not get a 500 server error or an xml error.
the page ate my xml error. anyway.. one last question then i'll go sleep...
can send-cb.cgi be anywhere? so long as XML/Comeback.pm is in the same folder? or does it need to be in mt.cgi directory?
___
the form isnt remembering all of my info just the name
> mt-cg.cgi in your base MT directory
I think that was supposed to be "mt-cb.cgi".
Your page is a wonder of nested DIVs in Safari, too. Kinda cool :)
Where did you get that blog script, it's really good