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.
There are times when you absolutely must run some plugins on a WP install, and you don’t want to allow administrators to be able to disable them. Here’s how…
Those who follow WordPress closely will understand that a vulnerability has been found that, whilst not being especially dangerous, could be very annoying for some.
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.
Very quietly we’ve been building something quite special for WordPress. We can’t say what it is right now, but something’s coming and we’ve done almost all of it with WordPress based technology.
It’s quite apt that on the day that WordPress.com appears to have broken (it’s not serving any front-end pages on this blog at the time of writing if you’re logged in) I’m making a post about hosting
There are some nice tricks inside WordPress, for example this WordPress Auto 301 Feature. Keep up the good work ladies and gentlemen!
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.
If you ever feel like you want to change the source of the news items on the wordpress dashboard (Not wordpress.com, sorry if I got your hopes up there) here is how to do it.
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.
Any website is a reflection of your business. If it’s cheap and unreliable, it’ll say that to your potential clients. Recently we’ve had client’s who’ve been burned by other web designers and their hosts