Today we have rolled out the newest version of Drupal, released recently: Drupal 7.22. This update contains no new functionality and no security fixes, but we're committed to keeping Drupal up to date to ensure it's running smoothly.
This affects you if you have a Drupal 7 site with us, although there is nothing you need to do, and neither you nor your visitors will notice any difference when using your site.
Today we updated Drupal to 6.28 and 7.19 to ensure security is kept up to date. These were releases made by the Drupal team to address minor security issues, and if you have a site or sites with us, you won't notice any difference in its day to day operation. If you do want to know more about the changes, or our security practice in general, do give us a call on 0800 019 9860 and we'd be happy to go into it!
Recently I was tasked with coming up with a system for redirecting users to the correct version of a translated site based on where they were accessing the site from. Having spent some time looking on Google and Drupal.org I did not find anything suitable and so decided to write my own which I am now sharing due to the lack of resources on this subject.
Acquia Dev Desktop is a great really lightweight AMP installation, it is really designed for newcomers to get up and running quickly. Here is how to adapt it to make it more flexible and get Drupal running FAST on a Windows development machine.
Download the Acquia Dev Desktop from the Acquia site: http://network.acquia.com/downloads/7.x/windows-installer. You can use the 7.x version or the 6.x, it doesn't matter too much, we will pull all that out.
If you write PHP on a Windows computer then setting up a reliable method for debugging your scripts will at some point be something you will want if not need to do for when simply writing out variables to the page will not do.
If you have ever wanted to add a quote box to the side of an article or add an image box with a caption, we have added a few standard templates to the Drupal 6 editor to use.
Suppose you want to start an Amazon EC2 virtual machine instance, but you want it to run from an EBS volume, so that the storage is persistent, and you don't need to worry about what happens if your instance terminates.
There are plenty of guides out there on how to convert an AMI (Amazon Machine Image) into a format that can be run from an EBS volume, instead of the volatile storage an instance usually runs from, but very few for how to get an instance to boot from an EBS. The reason for this is wonderfully simple, for a change.
For a while now, we've been looking for a solution to a common problem on Amazon EC2 hosting: how do you automatically create regular snapshots of your many EBS (Elastic Block Store) volumes, but also not create so many snapshots that it becomes unmanageable? We might have found the answer.
We use WAMP on a daily basis on our desktops for development purposes (I'd never recommend using it on live servers, its designed for development only). Trouble is it's been running like a dog for a long time, it finally got the better of me and I decided to do some research as to why.
The steps I took were a bit trial and error, but here's the run down of what worked for me.
When looking at global browser statistics, most people tend to focus on the whole rather than their target audience. A good average for this is the fantastic wikipedia entry which takes statistics from a whole range of sources: http://en.wikipedia.org/wiki/Template:Msieshare1. This claims that current global IE6 usage sits at a lofty 20%, certainly seems like something that can't be ignored.