Migrating a WordPress site can be something of a scary challenge, but we do it a lot, and we’ve become used to it. Here I show you the steps we take moving a localhost site to a live domain.
There’s been a big fuss lately over the latest WordPress hacks. One of the key things about security is to think about what happens when the first line of defence is breached.
On the night of June 23rd, Telegraph Media flicked the switch on a new project – Telegraph Blogs. And, proudly, we’d like to say we were involved with the project.
If you get this kind of weird behaviour, especially after a crash, it can be well worth looking through the tables for problems such as those in this post.
One thing we talk a lot about is how important it is for costs to stick to problems which have already been solved. Get fancy and do something new, and your costs have rocketed away.
It’s hard to measure the cost of code. Simple stuff can be ferociously time-consuming to develop, and bad coders often produce reams of poorly structured code.
The Museum of Computing needs a new home. If you, or anyone you know, has the capability to offer some real and useful help, then they’d love to hear from you.
I was working with a client recently on their own, customised installation of WordPress… and it was driving me potty. The lesson: Keep it standard. It makes life easier for all involved.
One thing worth thinking about in 2008, is fixing the DNS entry to your website. Most are probably set up just fine, but here’s one of the most common problems we see.
We’ve been writing custom themes for clients for quite some time now, and felt it was time to give something back to the WordPress community. So we built a GPL theme for hosted versions of WordPress.
Create an “.htaccess” file in the folder you want to be cached and add the following to it. This will have the effect of caching your site for a week.