LA Drupal Camp 2012- Maintaining a Drupal Site


Published on

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

LA Drupal Camp 2012- Maintaining a Drupal Site

  1. 1. LA Drupal Camp 2012Maintaining a Drupal Over the LongtermMeghan Sweet (@meghsweet)29 June, 2012
  2. 2. Site Launches!
  3. 3. Now What?
  4. 4. Empower Your Users
  5. 5. Drupal Web Team Training• Learning Drupal Takes Time• Train the Trainer• Backup Expert Level Support• Effective Documentation
  6. 6. Content Manager Training• Onsite Training Sessions• Help Videos• FAQ / Forums• Training Materials
  7. 7. DocumentationExtensive commentingOnscreen helpTraining VideosFAQ Capture
  8. 8. Support Best Practices
  9. 9. CommunicationTicketing ToolExpectation ManagementExpect Ongoing Education
  10. 10. QA Best Practices• Development, Testing & Production• Stakeholder Sign-off by Review• Regular Release Cycle• Batch work
  11. 11. Audits and MonitoringPrevention is better than cure
  12. 12. AuditingPeriodic Auditing is important!Make a check-list.
  13. 13. Auditing Code Base- Version Control- Development Server Setup: Dev > Test > Prod- Hacks- Hacked! module- Custom Modules- what do they do?- Contributed Modules- updates, errors?- Drupal Core- update and/or upgrade?
  14. 14. Auditing Configuration- Panels/Context/Display Suite, used properly?- Live Updating? Feeds?- Site Logs- Permissions and Roles- PHP filter- Spam Prevention- Performance Optimization- SEO: SEO Checklist Module
  15. 15. Auditing Theme- Are themes up to date?- Base Theme used? Or Hacked?- Custom PHP logic in tpl files?- Libraries and CSS structure- Responsive- What techniques?- Red flags- are tpl files out of control?
  16. 16. Monitoring- Most of the time in recovery is figuring out what’s broken- Monitor Trends
  17. 17. Monitoring- Use Syslog to write Drupal logs to text file- Monitor Servers, SEO- Cron-Total Admin Control or create admin views- Are your admins educated?- Every time you have an issue- start to monitor.-Google Analytics
  18. 18. Security Review- Most security holes are created in the configuration andtheme.- Security Review module will help!
  19. 19. Security Review- File system permissions- Input format- Content (nodes, comments and fields in Drupal 7)- Error reporting- Private file- Allowed upload extension- Database error- Failed logins- Drupal admin permissions- Username as password- Password included in user emails- PHP access
  20. 20. Training is key.Users need Drupal awareness!
  21. 21. Detecting Problems- Spam- number of nodes, emails being sent,comments, users. (Good to know trends)Mollom, Captcha, Admin Views- Use Version Control to check diffs- revertto good version- Hacked! Module - switch to unhackedcontrib module- Security Review Module will look for spamin content.- Use a good hosting company
  22. 22. Security & Module UpdatesWhat to do with those error messages?
  23. 23. UpdatesKeep on top of Updates- within 30 daysfor security updates.Read the update notes for non-securityupdates.Finding a bug in a contrib module.Do Not Hack Core! No exceptions.Planning for Custom ModulesStaying in tune with Advances inCommunity Modules
  24. 24. Version UpgradesTimingCommunity Catch-upNew ModulesConsider a Rebuild?TestingWhat’s the plan?
  25. 25. Community Connection
  26. 26. Groups.Drupal.orgInternal Knowledge SharingLocal User Group Meet-upsDrupal Camps, Cons & Summits
  27. 27. Taking OverAnother’s Work
  28. 28. discoveryread the documentationtalk to all stakeholdersget clear line of sight to prioritiesreview the laundry list
  29. 29. Key PointsContinual Love & AttentionKeep Documentation FreshUse good communication andfeedback/QA toolsFoster Drupal TalentCommunity Contribution
  30. 30. Thank You! @meghsweet@chapter_three