David Raynes

Update: This has been superseded by remote post - Release 2.

Here it is, folks! You can see remote post in action in my remote post Test Blog, or now in use at the official LazyWeb site.

Download the archive, either remote post.tar.gz or remote post.zip.

In the archive, you'll find three files:

• mt-pi.cgi: place in your base MT directory
• remotepost.pm: place in lib/MT/App/ directory
• ConfigMgr.pm: place in lib/MT/ directory

ConfigMgr.pm is a patched version of the MT 2.51 version. It contains all of the new configuration directives for remotepost and ComeBack.

To enable remote post on your installation, put the following lines in your mt.cfg file (only use remotepostScript if you have to change the name of mt-pi.cgi):

remotepostBlog blog_id
remotepostAuthor author_id
remotepostScript mt-pi.pl

Those are the blog and author remote post uses to determine where to place the new entry. They default to 0, so you should define them. :)

I should (hopefully) get remote post and ComeBack working together nicely by the end of the week. Until then, I'd suggest you setup the blog for remote post to not allow any comments on entries by default.

How To Send A remote post Ping

• Find the remote post URL for the blog (e.g http://blog.mediacooperative.com/mt-pi.cgi for LazyWeb)
• Write your entry
• Copy and paste the entire entry into the Excerpt field
• Save and ping away

Future plans for remote post:

• Integration with ComeBack
• Quickie web interface (instead of using Excerpt kludge)
• Multiple remote post destinations in one MT installation (i.e. like how Trackback works now)
• Category support:
  • remote post Category auto-discovery/advertisement
  • Multiple or Single category per remote post destination
• New MT Idea: ComeTrackBack? (Trackback ping received on a remote post posted entry)