This plugin just creates convenient tags you can use to drop javascript cookie functions into your template headers. Put <MTJavaScriptCookies> in the <head>...</head> section of a template to give you the whole menu of cookie functions: setCookie, getCookie, deleteCookie, and fixDate. Alternatively, you can go a la carte and use just what you need with the tags <MTJavaScriptSetCookie>, <MTJavaScriptGetCookie>, <MTJavaScriptDeleteCookie>, <MTJavaScriptFixDateCookie>.
To install, just drop it into your plugin directory, then put the tags in your head as needed. Finally, use the setCookie, getCookie, deleteCookie, fixDate functions in your javascript.
This plugin is used by my EntryEditLink plugin.
Please note that while I packaged the javascript in a plugin, I did not write the javascript. I ganked it from http://www.webreference.com/js/column8/functions.html.
The Search function (originally by Jay Allen), which has been incorporated into the standard MT corpus,
has a nifty tag, MTEditEntryLink, which lets the user edit an entry if he or she is logged in.
Unforunately, you can't use that tag except in your search templates, which makes it tough to use.
This plugin makes available a
This plugin will only work for blog's that use the same directory for data and MT. If your main index file is in the same directory as (or a subdirectory of) your mt.cgi file, you're good. Otherwise, the cookie detection doesn't work. There is a solution for this, but I haven't perfected it yet.
New for Version 0.2: smarter permission checking so you only get an [edit] link if you're logged in AND you have permission to edit this particular entry.
INSTRUCTIONS:
In addition to the standard Blosxom flavours, we used several flavours that we've put together on our own. We'll put them here for your consumption as we package them for use. If you have any questions or bug reports, please email James Vasile, the person that did most of the coding.
This flavour displays your entries and adds forms and buttons so you can send a trackback ping to other blogs without entering anything more than the trackback url. This saves on lots of cutting and pasting when you want to ping other blogs. Story.ping is the only interesting file in the package. Feel free to replace the head.ping and foot.ping as you wish.
This flavour is just like the Ping flavour above, but before it copies your excerpts to the ping form, it strips all the HTML. Requires the plain_text plugin, below.
Blosxom come with a built-in flavour for RSS Version .91. The only reason you need this mod is if you've installed my Default Template mod or if you want have several RSS versions in several different flavours and want to differentiate them.
Blosxom's default behavior is to throw an error if it doesn't recognize the flavour.
I've modified that behavior with a very small change to the source.
Basically, whenever it doesn't recognize the flavour, my version pulls from default templates (head.default, story.default, etc.), which are really just the HTML templates renamed. If the default template doesn't exist, it reverts to the original behavior (throw an error or use one of the templates from the script). Ideally, users should never see an error, even if the error is in the referring page or if they mistype a URL. Now users can see fewer errors.
The advantage of this setup is that if most of my content types are text/html, I only need a content_type file when my type is NOT text/html. Similarly, I have several story template, but I want them all to use the same default head and foot template. Rather than copy my flavour several times, I just made it the default. The few times I want to avoid the default, I just specify a different template.
Another benefit of this mod is that if everybody had default files, you could distribute new story templates (where most of the interesting flavour stuff is) and just let people use their default templates for the rest. The Ping flavour, for example, could have just been distributed as story.ping instead of a zip file containing several files.
Be aware that if you use this mod, your default flavour will override the builtin RSS .91 flavour. To fix this, download this zip file of the RSS .91 flavour and unzip it into your directory of flavours. Now the RSS 9.1 flavour will take precedence over the default flavour. You should decide whether you want to access these files as RSS or as RSS91. The original Blosxom distribution used RSS, but in light of the updated RSS specification, you should probabl go with my naming scheme and update your links.
If this mod interests you, change your load_template sub as below. The mod is for Blosxom version 2.0b3, but the same or similar change should work on other versions too.
sub load_template {
my ($path, $chunk, $flavour) = @_;
do {
return join '', <$fh> if $fh->open("< $datadir/$path/$chunk.$flavour");
} while ($path =~ s/(\/*[^\/]*)$// and $1);
do { #<-- add this line
return join '', <$fh> if $fh->open("<$datadir/$path/$chunk.default"); #<-- add this line
} while ($path =~ s/(\/*[^\/]*)$// and $1); #<-- add this line
return join '', ($template{$flavour}{$chunk} || $template{error}{$chunk} || '');
}
The last plugin I wrote for Blosxom, this one is a plugin that uses internal flavor files to display your posts and writebacks in a format that can be saved to a file and then imported into Movable Type.
This plugin allows you to automatically link back to people that link to your blog. It populates $referer::recent with the most recent referrers to your blog. It orders the list by number of hits referred and is smart enough to combines hits from different referrers but from the same domain. It won't detect hits from the domain on which your blog is hosted so that users don't see your obsessive reloading of your page. It also has the ability to let you specify pretty names for the blogs that connect to you so users see links to Bob's Blog instead of bob_blog.com or whatnot.
This is just a test plugin to help make sure your plugin setup works. Just drop it in your plugin directory and load your blog. You should see "TESTING...plugin found, loaded and run." above your posts. It might even appear twice. This will let you know that your plugins are being found, loaded, and run by blosxom. If you don't see those words, your setup is not working right.
This plugin uses Trackback pings to populate $now_playing::last with the last few songs you've played in Winamp. It requires Benn Trott's tb.cgi implementation of Trackback and the DoSomething Winamp plugin.
Configuration takes a few steps, but they're all easy.
After installation, play a few songs in Winamp and then load your blog. If you see a list of songs, you're done. If not, something got messed up. The first step to trouble-shooting is figuring out whether the pings are getting sent. Go to <http://yoursite.com/tb.cgi?__mode=list&tb_id=now_playing_plugin>. You should see some pings there, mainly blank ones with your song data in the excerpts. If you don't see them, the problem is in steps 5 through 10. If you do see the pings, then the question is why isn't the now_playing plugin putting that data on your page. The problem is in steps 1 through 4.
If you absolutely can't figure it out, drop me a line.
Thanks to A Whole Lotta Nothing for the inspiration.
This plugin populates $plain_text::body with a copy of $blosxom::body that has the HTML stripped. No config required.
This plugin is a modification of Todd Larason's categories plugin, versoin 0+1i. It builds a tree display of your blog's paths/categories and displays the number of posts in each category. I modified the plugin's output format for a narrower display. Todd tells me that later versions of his plugin include this option, so you might want to check them out. I'm keeping this plugin on my page because his later versions crash my system.
Enjoy.