scriptygoddess

JD just sent me this link to his site:

Script to rename your wp-admin folder.
As he says – it's not a foolproof method to protect your site, but certainly not a bad idea.

UploadBin
Kind of like pastebin – but for files, and Mark offers it up so you can download and host it on your own server.

wp-hashcash
A version of Spam Stopgam Extreme.
[seen on a lot of sites, but most recently on PhotoMatt and Weblogtoolscollection]

WordPress "Suggest" plugin
Kind of like "Google's Suggest" feature – for WordPress Searches.
[blogginpro]

WP-lists Plugin
Centralized List management (through wordpress?)
[blogginpro]

The WP-Gallery Plugin 0.1 offers a nice, easy way to include your Gallery albums and photos within a WP powered blog.

Earlier this week, the 1.2.2 version of WordPress was released. This release fixes a few bugs and security issues and is recommended for all 1.2 users. More about the upgrade in the WP Development blog. Wondering what files changed? Here's a list.

The last time I did any extensive web dev on the mac was about… oh, maybe SIX! years ago. Eek, I feel old. In any case, I've been doing everything on the PC since then, and while I have a number of really great tools on the PC that I like, I'm clueless when it comes to mac tools.

On the PC, the tool that I use the most is Dreamweaver. Not so much for it's "WYSIWYG" feature, that doesn't work too well for me, but it does auto-complete HTML tags, it knows php functions and can tell me what data types I have to pass in, does code highlighting. I even use it to make my stylesheets, because I can get it to pull up the "correct" way to write out a style definition if I forget (which is often).

So what tools do I need to do development on the Mac? I've downloaded a trial copy of Westciv Stylemaster which seems to give me what I need for writing stylesheets. I have BBEdit, but it doesn't do the auto-complete stuff like dreamweaver does (of if it DOES, I can't find it!).

Cany anyone make some recomendations? (Post in the comments please)

There's a pretty serious security bug with WP 1.2.1 (and the current 1.3 alpha), one that can make it so your blog is basically unusable (not permanently, as far as I can tell) but still – if you're using WordPress you should probably make this change.

In any case, here is how you fix the problem. It's a very easy fix. If you can search for text on a page, you can fix this problem.

I hesitated posting this, because I don't want to "start a panic" – nor do I want to give instructions on how to hack WP blogs. But I do think it's important that people go ahead and make this change.

[brought to my attention by Christine]

Need to bookmark this so I can find it again…

QuickTabPrefToggle
Adds some great preferences/options relating to tabs, etc. (for example, can force links that would ordinarily open in a new window in a tab in the background.

The author of that extension also has a few others too that look interesting. Here's the extensions homepage

Just saw this on the hackers mailing list:

User Comments Plugin
This plugin will moderate comments from users who are not registered and logged in users of the site.

WP iTunes
Display what's currently playing on your iTunes on your blog.
[via Weblog Tools Collection]

One of the things Christine had asked me to add to pixelog, was, when no "previous" entry was available – to have the text still show up, but be "greyed out". I remembered a post Alex King had made on the hackers mailing list about capturing the text that some functions typically echo into a variable. What he suggested was to do the following:

<?php
ob_start();
the_title();
$my_title = ob_get_contents();
ob_end_clean();
print($my_title);
?>

This was the trick I needed. Here's the code I used do the "greyed out" effect. (The issue here, if you don't know – is that next_post() will simply echo nothing if there is no next post)

<?php
//determine if there is a next post
ob_start();
next_post();
$nextpost = ob_get_contents();
ob_end_clean();
//now print the appropriate link or greyed out text
if ($nextpost) {
next_post('&laquo; % | ','previous','no');
} else { ?>
<span class="grey">&laquo; previous</span> |
<?php } ?>

(Yes I know I'm using the text "previous" with the next_post function… that had to do with her preference of displaying the photos)