Posts in "Uncategorized" category

Introducing DevKit for EE 2.0

I’ve spent the last 8 months developing modules (and templates) for EE 2.0. Pretty early I got annoyed by some of the redundant manual tasks I had to do over and over again .. so I started creating some addons to help me out. Now I’ve bundled (some of that) functionality in this thing I’ve named DevKit for EE 2.0, download it here: zip / github page.

For now it contains functionality to generate the skeleton of a new EE module – you just give it some details (name, description, etc.) and an installable EE 2.0 module will be generated. It will add some helpful functions as well. Then it’s up to you to fill it with business logic ;-)

Also it has a one-click load of snippets and global variables from the filesystem. Personally I like to use the built in EE functionality to add that to the main navigation at the top, so that when updating the global variables in my files I just hit that button and they’re all updated.

And then there is a YAML 2 dbforge generator that will help you out when you have a lot of database tables you need to generate (this is handy for the upd.yourmodule.php install() and uninstall() functions). Personally I’m too lazy to write dbforge code, YAML is quicker (see the screenshot). This is very basic, but it works.

Here are some screenshots:

DevKit: Create new module

YAML 2 dbforge Code Generator

Update/Import snippets/global variables from disk

Like it?

I hope that other EE developers find this helpful. If you do, please let me know, and also – if you’d like to contribute / help out improving this DevKit let me know and I’ll add you to the project on github so you can commit code to it.

This is a small step for EE, and a humble start, but maybe this can evolve into an awesome tool / framework for EE 2.0 development.


WooThemes launch of ExpressionEngine themes gets TechCrunch frontpage

Themes have moved


Please note that these themes have now moved to ThemeForest, you can find them here: ExpressionEngine Themes @ AddonBakery

Ok, I’m kind of busy these days so I haven’t got time for the most elaborate posts — but anyway, as some of you might know I’ve teamed up with WooThemes to create theme packages for my publishing engine of choice; ExpressionEngine.

Yesterday was a busy day since we launched it, and thanks to adii and Daniel Brusilovsky it made the frontpage on TechCrunch:

WooThemes and ExpressionEngine on the TechCrunch frontpage

I think that’s great, both for WooThemes and EllisLab/ExpressionEngine.

And of course, it also resulted in this:

The author’s tweet (300k followers) + TechCrunch’s tweet (1,3m followers) + general Twitter crazyness with the “” being passed around, resulted in the rsaweb guys working their butts off to keep the server up (it went down a couple of times as well, but all in all they did a good job).

It’s exciting times, since we’re basically testing out some new grounds here; is there a market for premium ExpressionEngine themes? Who knows. I hope so, and it’s going to be interesting to see how the traffic and hype converts to actual sales.

What do you think?

How to move a WordPress installation and keep linkjuice

Recently I went freelance and decided to rebrand myself – thus the need to move my blog from one domain to another. Of course, that meant moving the content to a new WordPress install, but also – since my old blog had a handy pagerank of 5 and lots of incoming linkjuice – I needed to redirect all this to my new blog. To make things even more complicated, I had decided to go away from my original link-format of “” to the shorter “”. Needless to say, I did not want to break existing links. It turned out to be a whole lot easier than expected.

First off, the WordPress export / import tool works like a charm[1]. Second, I wrote a simple .htaccess to forward everything to an index.php which then again redirects everything (including the query string) to the new url. That means for example will be redirected to .. and WordPress is smart enough to understand the original link-format, and then redirect to the new one I’ve chosen for this blog. So the user will end up on, all incoming links work and all link-juice transferred (using 301 redirects).


 header ('HTTP/1.1 301 Moved Permanently');
 $i = $_GET['i']; if($i != "") {$location = "" . $i;
 } else { $location = "";}
 header ('Location: '.$location);


RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?i=$1 [L]

Here’s the process in easy to understand list-format;

  1. Install WordPress on the new location
  2. Use WordPress’ built in export tool to do a full export of your original blog
  3. Upload the export file and use the same tool in the WordPress admin to import the data to the new blog
  4. Download and activate any plugins you had on your original blog (akismet, textile, etc)
  5. May be the case: go through all the blogposts and fix direct links to files etc. you have posted on your old domain (if such exists)
  6. Delete your old blog, and upload this new index.php and this .htaccess


[1] (unless you have large amounts of data)