Drupal in the Trenches Solving Real-World Problems

Register with us now to view the full version of this or any one of our valuable assets.
Register now
Already registered? Login.

Drupal in the Trenches Solving Real-World Problems

Systems fail. Websites crash. Sometimes you’re mentioned on Oprah. You need to act and act fast. Knowing how to troubleshoot decisively can save you time, money, and reputation when things go wrong. Join Kenny Silanskas (webkenny) from Acquia’s Client Advisory Team as we take a look at Drupal from the front line of enterprise level sites and discuss troubleshooting techniques that will change the way you see problems when they surface.

We’ll cover:

  • What is the problem? Simple question. Complex answer.
  • Why Drupal, Ogres, and Onions are the same. Peeling back the layers of any issue.
  • When to hack core. Getting your problems out in the open using the code.
  • How to debug. Using professional tools for the job.
  • When the fit hits the shan. Staying calm during critical situations.
Category: 
Publish on date: 
Thursday, September 22, 2011
Rating: 

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.