‘WordPress Hack’ Category

WordPress Plugin Repository – Trac

2
responses
by
on
December 21st, 2004
in
LinkyLoo, WordPress Hack

WordPress Plugin Repository: Now thats the way to organize and distribute plugins and also give plugin developers their due credit and provide a centralized repository! If there is no detailed tutorial on the dev blog soon, I might be inclined to write something up since I have been a newbie to Trac myself (which ROCKS, BTW) and have been messing around with it quite a bit. (looks like NM has made the same offer)

[Continue Reading...]

Spam Stopgap Extreme – Elliott Back

3
responses
by
on
December 21st, 2004
in
LinkyLoo, WordPress Hack

Spam Stopgap Extreme – Elliott Back: This is a late post since Stopgap extreme has been out for a while. However, this is a clever idea that I think might work well for now. In order to post a comment, the client MUST execute a javascript MD5. THanks Elliot.

[Continue Reading...]

WP: Archive by Date

2
responses

Mark produced Sortable Nicer Archives for WordPress but sometimes people don’t want the sortable part – a list will do. So due to a request in the WP forums, I’ve taken out the code that gets in the way for that, and made it just list by date. Can be seen working here in the latest WP build: http://www.tamba2.org.uk/T2/willitwork.php Download file: http://www.tamba2.org.uk/downloads/date_archive1point3.phps Download file (for 1.2 versions) http://www.tamba2.org.uk/downloads/date_archive1point2.phps Credit: Mark Any mistakes: Me 🙂

[Continue Reading...]

The 5 min WordPress anti comment spam hack

No
responses
by
on
December 15th, 2004
in
Cool Scripts, LinkyLoo, WordPress Hack

The 5 min WordPress anti comment spam hack: A quick and dirty shell scripty way to rename wp-comments files on your server. Useful ONLY if you are on a Linux/UN*X system.

[Continue Reading...]

Nightly Automation

No
responses
by
on
December 15th, 2004
in
LinkyLoo, WordPress Hack

Nightly Automation: A shell script to keep your WordPress blog synced with nightly builds. A terrible idea for production blogs. But if you want to help out the dev team by weeding out bugs and feel the need for pain, this is the script for you. Via: BloggingPro

[Continue Reading...]

WP Detective Plugin

1
response
by
on
December 13th, 2004
in
LinkyLoo, WordPress Hack

WP Detective Plugin: A translated link to a WordPress plugin that allows you to track a user as they traverse through your blog. This could be interesting if the data does not grow too quickly.

[Continue Reading...]

FlickIt

1
response
by
on
December 13th, 2004
in
LinkyLoo, WordPress Hack

FlickIt: More Flickr blogging goodness. Flickit is a plugin for WordPress and other CMSs (planned for the future) that costs $5 and allows you to add pictures to your blog, mostly aimed at Flickr. Try it out at the demo with username and password: flickit I would like to know how the “for pay” plugin works out for Colin. I am sure this will set some kind of a trend though I am not sure what the lisence implications are.

[Continue Reading...]

Spelling Checker plugin for WordPress

1
response
by
on
December 9th, 2004
in
LinkyLoo, WordPress Hack

Spelling Checker plugin for WordPress: Cool! My careless typing could sure have used this!

[Continue Reading...]

.NET based Feed Readers and WordPress 1.2

3
responses
by
on
December 8th, 2004
in
General, WordPress Hack

This was recently brought to my attention by Adam Messinger who had trouble accessing this blogs’ feeds through a .NET based feed reader. Apparently …this is caused by a known bug in WP 1.2, which produces HTTP headers that don’t sit well with .Net since a security patch released early this fall. Readers written with .Net refuse to process affected WP feeds, citing an “HTTP protocol violation.” An easy fix for this can be found at http://technospin.org/index.php?p=14. Apparently this has been addressed already in the forums and in the CVS from what I see. WordPress 1.2.1 DOES NOT have this fix, but the CVS and all 1.3 Alphas do have it. So if you are running WordPress 1.2 or WordPress 1.2.1 and have not applied this fix, I suggest that you open up your wp-blog-header.php and replace the “Last Modified” (at line 77) with “Last-Modified”. Thanks Adam!

[Continue Reading...]



Obviously Powered by WordPress. © 2003-2013

css.php