WordPress Dashboard Editor

Of the entire website the Dashboard is seen by administrators the most, but it is the hardest part of WordPress to customize. Well not anymore. This plugin allows you to add whatever you want to the Dashboard through PHP and HTML and allows you to even add Sidebar Widgets. You may also wipe the entire dashboard or individually remove some of the more irritating sections like the Dev news, Planet WordPress and the getting started section.

In WordPress 2.5, the code is cleaner, the plugin is more responsive and you can add both “real” sidebar widgets, or add “fake” ones to match the dashboard.

This plugin is currently intended for 2.5, but it also works in WordPress 2.1 – 2.3 and can work in WordPress 2.0.x if you use the Completely Wipe Dashboard option.

Installation is a breeze:

  1. Download the zip file for WordPress Dashboard Editor
  2. Unzip and upload dashboard.php to your wp-content/plugins/ folder.
  3. Go to your dashboard. There will be a new sub-menu item.
  4. Select any options you want and add any PHP or HTML code that you want to the textbox.

Code Examples:

To add a sidebar widget to your dashboard (after selecting the option from the Dashboard management page) use the code:
<?php dynamic_sidebar('admin');?>
The Admin sidebar is modified and controlled the exact same way as any other sidebar.

If you use the WP-UserOnline plugin you can use:
<?php echo useronline_page();?>

In WordPress 2.1-2.3 f you find that your new content doesn’t align nicely you can add:

<div style="float:left; width:460px;">
//Add all other content here

Any code that can be used in your WordPress Theme can be used in the dashboard. This means that you can have different information appear for the different user roles among other things.

Organizing WordPress Plugin Bug Reports.

One of the downsides of having a popular plugin is the amount of support requests, bug reports, and feature suggestions that come in. Well, it’s not that bad, but sometimes it’s difficult to organize what features should be added, what bugs must be tackled first, and what can just be ignored.

If you’re one of the few and the proud over at WP Extend Plugins, you have a nice tool at your disposal to keep track of all your plugin related needs. The tool, you ask? It’s the trac ticketing system over at the WordPress Plugin Repository.

From Weblog Tools Collection

For most of my wordpress plugins, like AJAXed WordPress I use SVN and the WordPress Plugin Repository to keep track of changes I make to my plugins between versions to make it easier to write the changelog, but I never considered using it for bug reports.

It would make it so much easier because I have a tendency to get bug reports and feature requests in emails, comments on the extend page, in forums, on the main plugin page, on its readme page. It gets so chaotic that stuff slips through all the time.

I’m on the verge of writing a Plugin to help me organize it all. ;)

Tag Management for WordPress 2.3

Now that you have gotten used to WP 2.3 and had time to fiddle around with all those tags, you are probably finding that you need to edit, rename or delete tags. While I was going to write my own Plugins for this for a while, I found the perfect Plugins to do the work for me — and by perfect I mean really good, so I take no responsibility if they eat your dog.

The Simple Tags has been around for a long time, but now it works perfectly with WordPress tagging. What does it do? Most everything you could want (I could retype the list, but I’m going to borrow it straight from the Simple Tags website):

  • type-ahead input tags
  • auto suggestion of tags
  • tags management (rename, delete, amalgamate, search and add tags, edit tags ID)
  • List of non tagged contents
  • Edit mass tags
  • Possibility to tag pages (not only posts) and include them inside the tags results
  • Related content since common tags
  • Possibility to add related posts inside RSS
  • Dynamic Tag Clouds with colors with Widgets
  • Tags inside your header’s blog
  • Embedded tags ([tags]tag1, tag2[/tags]) for retro compatibility

I use a lot of Plugins and write a lot of Plugins, so the fact that I even use one usually means it is really well made or very useful, but this one is one of the very few that I thought was good enough to promote. Remember, if you have a favorite Plugin, do the author a favor and mention it once or twice.

Oh and what would be really nice is if it had a feature that would suggest related keywords based on the text (there used to be a Yahoo API that did this.) Wink Wink.

INAP 3.0 Progress

Aside from a brief flirtation with a couple payed projects, I’ve been heavily focusing on rewriting the code for INAP 3.0, and it has almost reached the point of a private beta (which means I start running it on this site.) I have selected the new name for INAP 3.0, but I’m not going to reveal it just yet. Here is a small preview of what you can expect from INAP 3.0:

INAP 3.0 is now truly modular with a main Javascript/PHP core that other features hook into to function. This core is easily extensible and the new structure of a main project with many smaller projects will make bugfixes and upgrades less painful, and will allow the user to upgrade the plugin section by section as most changes in the modules won’t effect the core.

For the users:

  1. INAP 3.0 will make upgrades far less painful. With each section managing its own options there won’t be the constant changes to the way little things work.
  2. Features will flow more freely, and individual sections will reach maturity faster.
    Individual modules can be deleted without effecting the rest of the plugin. his will help speed up your WP.
  3. Most bugs and irritants in the current version of INAP have been removed including the entire reload of the comments section when a comment is posted, the extra text added to links has been minimized, the built in effects have been improved, and the entire plugin is faster and easy to use.

For the developers:

  1. INAP 3.0 core now works off of advanced PHP/Javascript/XML and can easily be extended with custom modules.
  2. The new license is less restrictive that the previous versions.
  3. INAP 3.0 provides a framework that other plugins can hook into to harness its maturity and the hundreds of hours that have gone in to its development.
  4. Global variables have been almost entirely eliminated from both the Javascript and PHP—INAP 3.0 will play nice.
  5. The Javascript core is entirely independent of the AJAX library used which means that any AJAX library (jQuery, Prototype, Mootools, etc) can be used and and INAP 3.0 will function just as well. Adding new libraries is no harder than adding a couple lines of code.
  6. A few well placed actions and template files can make any theme compatible.

Multi-plugin Plugin

Multi-plugin is a very simple script that allows you to add small bits of PHP scripts, such as WordPress filters, without having to make a plugin for them.

Download Multi-plugin

Installation is as simple as renaming the file to .php, uploading it to your server, activating it, and adding some script to the textbox (for example, I use the following code to remove the nofollow attribute from comments.)

add_filter('get_comment_author_link', 'aoi_follow');
add_filter('comment_text', 'aoi_follow');
function aoi_follow($link){
   return preg_replace('/(<a.*?rel[^>]*)nofollow(.*?)/','${1}${2}',$link);


You can also use the following to add the trailing slash back onto feeds, categories, pages, etc. in WordPress 2.2+.

add_filter('user_trailingslashit', 'aoi_slashit',10,2);
function aoi_slashit($string, $type=''){
  if($type == 'page' || $type == 'category'|| $type == 'month'|| $type == 'day'|| $type == 'paged'|| $type == 'feed'){
    return trailingslashit($string);
   return $string;

WordPress Code Escape

Here is another small modified plugin that auto-escapes your code, nicely displays line numbers and uses valid XHTML. This plugin is based off of SemCodeFix, and adds many of the features I wanted in my code plugin.

Wordpress Code Escape

Download the file and save it as a .php file.
Upload to your plugins directory.
Activate it.
You may optionally choose to add the following style information to your theme’s style.css.

.code_child {
	font-family:"Courier New", Courier, monospace;
	background-color: #F4F4F4 !important;
	border:1px inset;
ol.code_child li{
 	padding:0 !important;
 	line-height:100% !important;
 	margin-bottom: -8px;
 	margin-bottom: expression(5 +"px");
 	margin-left:  expression(35 + "px");