Consider this a pseudo-WebMD page for diagnosing your broken Drupal Website. The Symptoms

  • Is your Drupal Website "broke"? Missing functionality? Crashing?
  • Do you have a looming launch date that keeps you awake at night?
  • Is your business poised to lose more than revenue due to an "unlaunchable" application?
  • Are your stakeholders demanding a plan to get it back on track - NOW?

If your Web application is experiencing performance issues, lacking critical functionality, or is stalled altogether, you're not alone. Accepted IT project success rates hover around 20-30% success, based on the most optimistic interviews. The bottom line is that 7 out of 10 IT projects "fail" in some respect. Rise above the statistics. The CommonPlaces Rescue (CPR) program provides a fast, unique service to help you quickly "breathe new life" into your stalled projects. The Causes Although each project is different, the most common reasons for a Drupal project going awry include:

  • Drupal Core is out of date or compromised: Drupal Core is the heart of your application - you need to maintain the latest version and ensure that the core code has not been compromised (hacked) in any way. Even small code change to core can cripple your site (and your budget) going forward, ultimately resulting in dangerous security risks.
  • Insufficient Architecture/File System: Development is often begun with one set of expectations, and business needs evolve to accommodate new or long term goals. Fact is, your site should be built to scale from the beginning. ItŒÍs always much easier (and more cost effective) to build-in or build-for the future from the beginning. You usually wonŒÍt find these issues until something breaks or something can't be done - and its extremely expensive to retro-fit your site to make it work.
  • Modules Matter: If Drupal core is the heart, the modules are the muscle behind your Web application. They are one of the reasons you chose Drupal in the first place and critical to the success of your project. However, since they are not part of Drupal core releases they may or may not have optimized code/functionality. You need to know if your modules are implemented correctly and are following Drupal Best Practices to be portable, upgradable and secure.
  • Inexperience: Some developers and outsourced firms are phenomenal at implementing Drupal for social publishing and communities. But when it comes to extending your Drupal with complex custom modules, multiple e-Commerce workflows, or integration with 3rd party applications such as data mining or content delivery networks (CDN) for streaming video - you usually need a team of experienced Drupal Rock Stars to pull it off. Trusting your business to inexperienced teams usually costs much more than money in the long run.

Treatment The CommonPlaces Rescue (CPR) program helps enterprise clients and start-up ventures to quickly get their Drupal-based applications working the right way to get your project online and market-ready in record time. WeŒÍll work with you and your team to triage your current site, prioritize and implement immediate fixes, and close high security risks. You'll receive a detailed Road Map of what needs to be done, and when, to get your site launched and profitable - and isn't that why you started this project in the first place? For a friendly and knowledgeable consultation, call Ben Bassi at 603-329-6760, ext. 101 to discuss your "symptoms" and discuss similar CPR cases - it always helps to hear that others have been in your shoes - and they turned their projects around with CPR. Or request more CPR program information in our contact form.

Hope your Drupal Website is feeling better and off-to-market soon!

Sherrin Bull

Leave Your Comment