Using the .htaccess file, you can force www or non-www URLs using the following snippets that should appear ABOVE any other code in your WordPress .htaccess.
As forcing HTTPS on sites becomes more and more important, I wanted to document the process in Drupal 7 for myself (and anyone else who might find it helpful!).
Drush and all that notwithstanding, I’m constantly downloading these two things separately because I can’t just tick the checkbox and let Drupal auto-update them.
A few weeks ago, I launched a new utility called DrupalVersion.com. It has one simple purpose: find out if your sites are up to date with the latest version of Drupal (6 or 7).
Last year around this time I posted an article here that wrapped up 2013 and set some goals for 2014. The slate has once again been wiped clean for the new year, but now’s as good of a time as any to reflect on the past year and set new goals for the coming one.
As a site developer for a web development agency, I often have the need to send clients pieces of content (pages, blog posts, team bios, etc) for review. These are pieces that cannot yet be live in the site, so they need to remain unpublished and be reviewed.
Sending links to clients with a login string in the URL is a great way to speed up the process, but I had to write a module to iron out the wrinkles for our clients.