admin-only navigation bar to bridge several projects

Sometimes I want the home page of a project to look different to administrators than to regular users.  For instance, on a couple projects of mine I was integrating several different technologies, osTicket, osProject, and WPMU — each one of these has different locations for their administrative use, so it is therefor useful to have a navigation bar so administrators can toggle between locations as needed.  The thing is, we don’t want that navigation bar to show up to regular users because it would just confuse them as they don’t have access.  So… and this isn’t brain surgery, I just add the following code whereever I want the navigation bar to show up.  My personal preference is in the footer file of whatever theme I’m using:

<?php wp_register(”,’  <a href=””>Support Admin</a>  <a href=””>Project Admin</a>’); ?>

You have to change the http addresses to correspond to YOUR projects of course, just hope this serves as a nice template if you need to bridge several projects with a cloaked navigation bar.

LaunchPad tweaks for WPMU

LaunchPad is a great WordPress theme for parked domains — allows you to accept requests for rss subscriptions to your site while you are still in development, thus you can build a database of people interested in your website before you even launch.  I’m using it with a WPMU project of mine and had to tweak a couple of the files to get the functionality I liked.  Here’s the files and the changes:

themes/launchpad/index.php      changed around line 29 that read:

<p class=”rss-subscribe”><a href=”<?php if($lp_feedburner_address) { echo $lp_feedburner_address; } else { bloginfo(‘rss2_url’); }?>”


<p class=”rss-subscribe”><a href=””

obviously put in your own domain name where it says

I also changed the footer to be kind of an advertisement for myself as the developer of the project, by changing around line 42 from:

<p>Powered by <a href=”” title=”WordPress”>WordPress</a>, <a href=”” title=”Google FeedBurner”>Google FeedBurner</a> and <a href=”” title=”A ThemeShaper Theme”>ThemeShaper</a>.</p>


<p>Powered by <a href=”” title=”WordPress Mu”>WPMU</a>, php/mysql application development and customization by <a href=”” title=””>iWebspider</a>, lead developer <a href=”” title=”Stefan Christain Densmore”>Stefan Christian Densmore</a>.</p>

matrix rain code

Here’s the code used to the display the matrix rain, thanks

<p align=”center”><img src=”” alt=”matrixrain” height=”400″ width=”600″ /> </p>

This code can be placed in .php or .html documents, works for pages and posts in wordpress, and can be added to .css files.  Fairly easy for novice users, send a post if any questions.

Sweet Skin Color Hack for wp-forum plugin

This hack can be used with any of the skin themes that come with the wp-forum plugin by Fredrik Fahlstad, but looks best with “sweet”.  This hack changes the color of the title bars and large folder graphics, and requires an image editor with a gradient tool (for the folder graphic to look best), I used photoshop.  3 files are hacked in the wp-forum/skins/sweet/images folder: folder_big.gif, cellpic3.gif, and cellpic1.gif.

Its pretty self explanatory once you know which files to edit and open them in an image editor.  Just change their color, then re-upload to the images folder where you found them.  The hardest part for a novice image editor is using the gradient tool to get the folder image to look nice.  Here’s a hint: you can combine the use of the lasso and gradient tool to capture the color area you want to change.

I had to hit refresh twice, per file change, on my browser (Firefox) to see the changes employed.

wp-forum skin hack for mu

These are directions for hacking the wp-forum plugin to work with wordpress mu.  The need for the hack derives from problems trying to change sub-blog forum skins.  Using the admin interface, you can change the main blog skin from the default setting, but not any of the sub-blogs.  Basically anytime a sub-blog tries to change the skin of their forum, it not only fails to do so, reverting back to the default skin, but actually changes the forum skin on the main blog instead.  The current work around that I’m using allows EITHER all sub-blogs and the main blog to have the same forum skin (other than the default skin), OR the main blog forum to have a different skin from uniform skin that all the sub-blog forums have.  [Note that the later of these two options DOES NOT STOP THE PROBLEM of users with admin privileges on sub-blogs from changing the main blog’s forum skin accidentally. ]

The hack can be done prior to uploading the plugin, or by directly editing the files live.   Basically you are going to replace the default skin.  The plugin comes preloaded with three skins to choose from aside from default: sweet, tiger, and web2.  Delete the default skin folder.  Open up the folder of the skin you want to use and edit the style.css file, changing line #2 where it says “Skin name: whatever” to “Skin name: Default”.  Then change the name of the folder to Default and you’re done.   The skin folders are located at  /wp-content/plugins/wp-forum/skins/

If you want the main blog’s forum skin to be different from the uniform sub-blog forum skin, select the skin you want in the admin interface.  If you want all the forums skins to be the same, and thereby disable sub-blogs ability to accidentally change the main blog’s forum skin, delete all the skin folders except for the new default one.

The original plugin, written by Fredrik Fahlstad, can be found at

Dust-317 flickr tweak

The file to edit is located at themes/dust-317/left-sidebar.php of your installation.

Line 11 of assigns the flickr user id (this is NOT the same thing as your flickr login id, see below). Replace the string 75017260@N00 with your own string.

You can find the string you want by logging into your flickr account, clicking on the link that says “you” or “your photos”, and then looking at the address line of the URL:”yourStringIsHere”

my string is 22879692@N04