The day to day goings on of Interconnect IT that we think are worth sharing with our readers.
After nearly three years in our office in Slater Street, we’ve reached the stage where we need better, more professional facilities. We’re off to Liverpool Science Park!
If you’ve been involved in WordPress over the past few years you’ll have seen it change from being an excellent but limited blogging platform into something more complex.
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.
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.
Here’s the presentation given by David Coveney at WordCamp UK 2009 in Cardiff. It covers the advantages, problems and implementations of WordPress as used by the News & Media sectors.
It’s been an exciting year at interconnect/it. We’ve worked on some large scale sites such as The Telegraph Blogs and Telecoms.com. So this year we’re giving two presentations at WordCamp!
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.