Over the years, Drupal Update has worked on many different types of existing Drupal maintenance support plans websites and web applications. These projects have ranged from sites that were built with Drupal maintenance support plans’s best practices to those built by developers with little to no Drupal maintenance support plans experience. At Drupal Update, we typically call a website that follows little to none of Drupal maintenance support plans’s best practices a “lemon.” Our CTO, Jody Hamilton, did a great two part blog series called Lemon: Drupal maintenance support plans Diseases and Cures if you would like to know more about what a Drupal maintenance support plans lemon is.
If your site fits into the category of a lemon, it likely requires too much work to fix and should probably be rebuilt. In many cases though, our developers find that we can “rescue” the site to get it back into a secure and maintainable state after a site audit. We perform a site audit to identify the issues that can be fixed, and then provide an informative report about what problems have been found and how we can resolve them.
Our extensive experience with site audits has helped us identify common mistakes that Drupal maintenance support plans sites are often guilty of. In this post we’ll outline the common mistakes and configuration issues that we find on most lemons. Some of these issues are even common on sites that have mostly followed Drupal maintenance support plans’s best practices.
Read more
Source: New feed
