Wordpress

[wp-readme-parser url=”http://svn.wp-plugins.org/disable-user-gravatar/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/disable-user-gravatar.zip”]

I found a little niggle in WordPress when creating a custom form using shortcodes and plain PHP/HTML for processing. Turns out if your form uses $_POST[‘name’] in your form, WP does not like that and serves a Not Found (404) page. Changing that input field name to a different one, say surname, fixed the problem immediately. Took me a good 30 minutes to figure that out!

[wp-readme-parser url=”http://svn.wp-plugins.org/twitter-goodies-widgets/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/twitter-goodies-widgets.zip”]

I’ve had the unpleasant experience of having to play and experiment with syntax highlighting plugins for any code I’d like to post on here and other blogs. Unfortunately, there’s a ton of options to choose from and many just aren’t up to scratch.

What’s worse is that some have funny syntaxes such as using <pre class=”language”> tags which are easily broken by the wordpress WYSIWYG editor and your code gets mangled. Not only that, but changing over to a better plugin becomes a tedious task if you have to change all those pre tags to shorttags.

I’d like to recommend a plugin which works very well, called SyntaxHighliter Plus by Fred Wu and other contributors. In my opinion, it’s one of the easier plugins to use and makes posting code a breeze.

[wp-readme-parser url=”http://svn.wp-plugins.org/localhost-notify/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/localhost-notify.zip”]

[wp-readme-parser url=”http://svn.wp-plugins.org/login-with-ajax/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/login-with-ajax.%TAG%.zip”]

Update: As of BuddyPress 1.1 this can be done via the wordpress aministration area. You can find this in BuddyPress > General Settings on the left side menu.

Those that use BuddyPress along with their WordPress MU installation may have found some limitations with the xprofiles. BuddyPress Devs have improvements listed as an upcoming feature, but in the meantime some things need to be fixed NOW!

One particular feature I needed to get round was the fact that you can’t change the default “Name” field. Whilst very common to have this as a field in most installations, we should at least be able to edit the field names the user sees, but unfortunately this is not so.

[wp-readme-parser url=”http://svn.wp-plugins.org/digg-this-button/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/digg-this-button.zip”]

Imagine you have a blog which is a supplement to your site, such as a platform for company news.

Now imagine you want to add your blog to your main site’s navigation menu. Easy enough, just add a static link.

Now imagine you want to create an unordered list of the categories in your blog, so that each category can be easily accessed from any page on your website…. oops, it just got tricky.

[wp-readme-parser url=”http://svn.wp-plugins.org/remove-buddypress-adminbar/trunk/readme.txt” download=”http://downloads.wordpress.org/plugin/remove-buddypress-adminbar.zip”]