- 5 minute install. Seriously.
- Install a new theme for your blog from inside WP. No need to mess with FTP clients and uploading files and stuff. Easy peasy.
- Tons of free and open source themes to choose from.
- Plugins allow endless possibilities. Whatever you are looking for probably exists already. Facebook/twitter/whatever integration, fancy widgets, syntax highlighting for code, caching, Google site map generators, you name it.
- Install plugins without leaving your WP admin page. No geek skills required.
- Comes with an automated backup plugin. Backup your database and email it to yourself daily. Do this!
- Upgrade your WP installation with 2 clicks. Maybe 3 (didn’t actually count, but it’s just clicking).
- The layout is super-flexible. 1, 2, 3 columns? None? Make your site look like less like a blog and very CMS-like? No problem. There are themes for all that.
- PHP & MySQL hosts are everywhere. You’ll have no trouble finding a host at all. If you don’t want to do your own hosting, you can always create your blog at wordpress.com.
- It’s Open Source and has a huge community. This means that WordPress will never die! *stabs and Amen break start here*
Mobile! It’s the latest and greatest of the buzzes isn’t it? But it’s damn right too, because more and more people are starting to use their mobile devices to reach out into the fabulous and marvellous inter-webs to do all sorts of productive things like using twitter, visiting reddit, tumbler and 4chan or read interesting articles on websites and blogs (probably being posted in their twitter stream) about kittens.
So let it be known that in the year 2010 A.D. you better bloody well have a mobile version of your website online or you’re going to miss out. Well, maybe not miss out, but you won’t be one of the cool kids (see photo) for sure! So how do you join the club of the hip and mobile-ready web sites?
Lot’s and lot’s of programming, l33t CSS skills and plenty of testing on all sorts of devices will get you there.
Or if you’re running a WordPress blog, you can also check out these two plugins which basically turn your old fashion 2009 blog into a futuristic mobile-touch-screen-enabled piece of awesomeness!
- WpTouch: turns your blog into it’s touch-friendly html self and allows people with iPhones and Android devices (among others) to easily tap and click around with their greasy thumbs.
- WordPress Mobile Edition: the name sort of gives it away doesn’t it? This baby enables those poor sobs who still have and oldskool smartphone without a touch-screen to use your site as well.
You can run them both to make sure you aren’t missing a single mobile hit on your site.
If you’re a blogger and feel like sharing how and why you’re doing it (blogging that is) feel free to fill out the Technorati state of the blogosphere survey for 2010.
The results should be interesting and available somewhere this november.
A while ago I found out some of my older posts were cut-off in the middle of a sentence or even in the middle of a word. Turns out that somewhere along the way of performing WordPress upgrades the MySQL tables’ collation had changed from a latin1 variant to utf8. Turns out that this conversion doesn’t work without it’s flaws and ends up cutting off your posts where “special characters” are used in the text. So if you use a word like “trés” your post suddenly ends with “tr”…
I wasn’t very happy with that as you can imagine. What’s even worse is that this kind of data corruption is hard to detect as well. I ran into it by accident while dishing up an old post to link to. How many more of my posts were also mangled like this? So it was time to dish up some SQL magic to help and figure out how big the damage was.
I ended up writing this simple statement which detects any posts not having their last character in a list of characters which typically end a post. A dot for example as a last character indicates a full sentence and without a space after it chances are big it was the last sentence as well. The query also displays the last 50 characters of the post which allows you to judge if a post really has been cut off or if it’s a false positive.
SELECT id, right(post_content, 50), post_content
WHERE right(post_content, 1) NOT IN (".", "!", ")", "?", ">", "]") AND post_status = "publish"
All I needed after this was a backup of my database that still contained an intact copy of the affected posts. Luckily I have been using the WP backup tool to email me a database backup every day since 2007 so that wasn’t a problem. To restore the content of the posts I transformed the SQL insert statement from the backup to an update statement looking like the following to update the post back into it’s original state:
SET post_content = '<Old post content goes here>'
WHERE id = <id>
The special characters in the post were in most cases transformed into blocky question mark symbols when reloading the post in the WP editor. So after some manual labour to reset those into the proper characters the post was ready to be republished and finally restored. Yay!
So this proves once again that there’s no such thing as too many backups and that collation issues are a bitch for all developers out there. Some tables are still in latin1 so I think I’ll have to convert those at some point to utf8 to be safe. But that’s something for later.
<p>” paragraph tag to be inserted causing it to become invalid.
- Using CDATA tags as proposed by some does not prevent the paragraph tags from being inserted when white-lines where used. Once you save your post or page the editor will wrap the code in CDATA tags anyway, but that doesn’t cause any problems.
- HTML tags in strings used in the code caused the tags to be filtered out by the WYSIWYG editor.
So how do you get it to work then without having to install any additional plugins?
- Don’t use empty lines in-between the code lines. It’s annoying to read since it’s all packed together but you can’t avoid the paragraph tags from being inserted any other way.
- To avoid the HTML tags from being removed from the string data you have to break up the HTML tags so the editor’s regular expression matches don’t catch them any more. For example instead of the string ‘
<br />‘ you use
'<' + 'br />'.
- Write and test the code in your favourite editor and browser. Once it works, apply the above changes to your code to make it work in your post or page.
Another option is to put all your code in an include file, include it in your post and simply call the necessary functions. The advantage of this approach is that it makes your code more manageable and easy to update. The annoying part is that all code isn’t safely embedded in your post so you have to maintain an extra file on your server which you might forget when you’re backup things up or switching hosts.
For a while now I was getting pretty tired with my old blogging theme, and wanted to restyle the whole thing. For the new theme I wanted to be able to use widgets, which makes changing your layout so much easier. I also wanted to use the extra screen real estate everybody has nowadays by broadening the columns up a bit, and have the content adapt to the screen size.
Since I like minimal themes I went for something without a lot of images in it. I still like gradients, even though I’ve heard they’re so 2007, but I used them nevertheless. I’m not a graphics artist, so a wicked looking vintage or cool scruffy looking layout isn’t up my league anyway. Gradients are super easy to do in GIMP btw, which makes my life so much easier, and I like that.
The theme itself is based on SandBox, which is awesome. Building a good theme from scratch for WordPress is pretty hard and wasn’t my ambition anyway, and SandBox sure makes it easy to concentrate on style alone. Another SandBox theme I drew inspiration and CSS examples from is Takimata. This is probably one of the most original SandBox themes around, and is definitely worth a look if you’re looking for something different. I almost used this one as is.
To see the theme in all its glory any browser except Internet Explorer will do. Thanks to Browsershots I tested the new layout on more browsers than I can remember, and IE is the only one that isn’t displaying the geeky looking slashes in front of the titles. Check the screenshot if you’re not on a kick ass browser btw.
Some tweaking will probably be done in the next few weeks, but with the widgetized sidebars, that’s possible without having to change a single line of code, which is awesome.