So you're launching a new website or replacing an old one and want to make sure everything goes smoothly? This guide will give you a run-down of everything you can check to avoid common pitfalls!
You should always start by checking the status report (http://example.com/admin/reports/status). This page shows you all of the basic requirements for your Drupal site to run correctly.
Any issues will be highlighted in red and typically have a link to a configuration page or the documentation to help you resolve the problem.
Drupal 7 will run scheduled tasks (known as cron jobs) out of the box, but only when users are visiting your site.
This is great for small sites which don't need much housekeeping, but if your site is a bit bigger or if you don't have visitors 24/7, you should set up a cron job to run periodically.
You can also look at a module such as Ultimate cron which gives you fine grained control over when each scheduled task will run.
If you use any of these services on your website, you should ensure that you've registered your real domain name with the service and you've updated Drupal with your new API key.
It can be easy when copying and pasting to accidentally link directly to a file or image on a development site.
These links can often stop working or perhaps worse, may direct users away from your live site and onto the development site instead.
You can use a module such as Link checker to ensure this doesn't happen, and it is good practice to password protect your development website, so that users (or more likely Google!) cannot stumble accross it.
See our series on High Performance in Drupal for some expert tips - High performance in Drupal Part 1: Give your site a boost and High performance in Drupal Part 2: Lightning fast code.
Development modules such as devel can often reduce your website's performance, so it's worth turning them off on your live site. You can still keep them running in your development environment if needed.
Many of us are guilty of using a common or simple password to make life easier when building a website.
Once the site is live, it's worth taking the time to update any administrative accounts with secure passwords.
It is also worth removing any unnecessary development accounts and content. Just in case.
Being able to see debug messages and errors are handy when creating a site, but may scare off users once the site is live.
Ensure that errors and warnings are hidden by visiting the Logging and errors config page.
The site information config page holds all of the most common site information, such as the website name and email address.
It's worth double checking that all of this information is correct. It could be quite embarrassing if your first newsletter arrives from firstname.lastname@example.org.