Your SlideShare is downloading. ×

EECI 2011 Workshop: Debugging EE

1,723

Published on

These slides are from the workshop during Dev Day at EECI 2011. They contain some tips primarily centered around the following article: …

These slides are from the workshop during Dev Day at EECI 2011. They contain some tips primarily centered around the following article: http://focuslabllc.com/blog/troubleshooting-expressionengine

During the workshop I demoed each "problem -> solution" so some context is lost with the standalone slides.

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,723
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
50
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. DEBUGGING EESITE PROBLEMS ERIKREAGAN • EECI
  • 2. WHO IS THIS GUY? Partner & Lead Developer2 ERIKREAGAN • EECI
  • 3. FORMAT Sample problem Debugging process3 ERIKREAGAN • EECI
  • 4. STEP QUESTIONS • Verbally speak the problem • Have you seen this problem in the past? • Have you read about or hear someone talk about this problem?4 ERIKREAGAN • EECI
  • 5. STEP QUESTIONS • What are the symptoms? • I have incorrect content displaying • No content is displaying • My template not rendering as expected • All URLs show my site’s home page • I see the “white page of death” on certain pages5 ERIKREAGAN • EECI
  • 6. STEP CONFIRMATION • “Is it plugged in” • Clear your cache • Try multiple browsers / computers if necessary • Log in as the user who experienced the problem6 ERIKREAGAN • EECI
  • 7. STEP CONFIRMATION • Based on the symptom(s), what do we know about the problem in the past? • Log debugging issues for future use and refer to them later.7 ERIKREAGAN • EECI
  • 8. STEP MAKE CHANGES • Begin to change things to find the source of the problem • Template code • Channel Entry (or related module) data • System setting changes8 ERIKREAGAN • EECI
  • 9. SAMPLE PROBLEMS9 ERIKREAGAN • EECI
  • 10. PROBLEM Verbal review of the problem: I have the 10 most recent “News” entries on my sidebar, but they don’t show up on some pages.10 ERIKREAGAN • EECI
  • 11. PROBLEM THE QUESTIONS Have you seen this problem in the past? (If you’re Lisa Wess you probably have dreams (nightmares?) about this problem, they’re so common.) • If so, what was the solution to that problem? • If not, it’s time to start making changes.11 ERIKREAGAN • EECI
  • 12. PROBLEM THE SOLUTION Add dynamic=”no” to the {exp:channel:entries} loop parameters so the URL doesn’t determine what results are returned in the sidebar.12 ERIKREAGAN • EECI
  • 13. PROBLEM Verbal review of the problem: I’m making changes to my template flat file, but they aren’t appearing on the website.13 ERIKREAGAN • EECI
  • 14. PROBLEM THE QUESTIONS Have you seen this problem in the past? • If so, what was the solution to that problem? • If not, it’s time to start making changes.14 ERIKREAGAN • EECI
  • 15. PROBLEM CONFIRMATION • Check database details • Clear the cache • Try updating a different template (narrow the search)15 ERIKREAGAN • EECI
  • 16. PROBLEM THE CHANGES • We have unexpected template / display output • Start with enabling the template debugging option • What is different between templates that work, and the one that does not? • Goes back to your experience and what you remember or have logged about previous problems16 ERIKREAGAN • EECI
  • 17. PROBLEM THE SOLUTION The template that wasn’t showing changes was flagged in the database to not be saved as a flat file and thus our changes were not being displayed. Switching the template to be saved as a flat file fixes the problem.17 ERIKREAGAN • EECI
  • 18. PROBLEM Verbal review of the problem: My channel:entries loop isn’t returning the expected number of results.18 ERIKREAGAN • EECI
  • 19. PROBLEM THE QUESTIONS Have you seen this problem in the past? • If so, what was the solution to that problem? • If not, it’s time to start making changes.19 ERIKREAGAN • EECI
  • 20. PROBLEM CONFIRMATION • Check number of results with CP filter (if possible) • Clear the cache20 ERIKREAGAN • EECI
  • 21. PROBLEM THE CHANGES • Review the query being executed • Manually run the query yourself if needed • Update the channel:entries parameters to modify the query being executed21 ERIKREAGAN • EECI
  • 22. PROBLEM THE SOLUTION ExpressionEngine defaults to limiting Channel Entry loops to 100 results for performance reasons. Because we want over 100 results returned in a single loop we had to add a limit=”x” parameter to the tag.22 ERIKREAGAN • EECI
  • 23. PROBLEM Verbal review of the problem: My entire site is nothing but a “white page of death.” I can log in to the CP, but the front-end isn’t displaying.23 ERIKREAGAN • EECI
  • 24. PROBLEM THE QUESTIONS Have you seen this problem in the past? • If so, what was the solution to that problem? • If not, it’s time to start making changes.24 ERIKREAGAN • EECI
  • 25. PROBLEM CONFIRMATION • Make sure it’s not just a single template • Clear the cache • Review any recent repository changes • Recall any recent database changes25 ERIKREAGAN • EECI
  • 26. PROBLEM THE CHANGES • Enable all debugging • Template debugging • Output profiler • Debug setting in EE • $debug variable in index.php26 ERIKREAGAN • EECI
  • 27. PROBLEM THE SOLUTION A newly implemented plugin, CI Helpers, had a bug in its plugin file. Turning on our debug settings allowed us to see the PHP error and fix the problem.27 ERIKREAGAN • EECI
  • 28. PROBLEM Verbal review of the problem: My entire site is nothing but a “white page of death.” This time it’s even the control panel. I can’t access the CP to turn on any debug settings or see what’s wrong.28 ERIKREAGAN • EECI
  • 29. PROBLEM THE QUESTIONS Have you seen this problem in the past? • If so, what was the solution to that problem? • If not, it’s time to start making changes.29 ERIKREAGAN • EECI
  • 30. PROBLEM CONFIRMATION • Review any recent repository changes • Recall any recent database changes30 ERIKREAGAN • EECI
  • 31. PROBLEM THE CHANGES • Disable extensions to see if that helps • Enable all debugging in your config file • Template debugging • Output profiler • Debug setting in EE • $debug variable in index.php31 ERIKREAGAN • EECI
  • 32. PROBLEM THE SOLUTION A newly implemented extension had a bug in the code. Disabling extensions allowed us to determine it was an extension causing the problem. Turning on our debug settings allowed us to see the PHP error and fix the problem.32 ERIKREAGAN • EECI
  • 33. QUESTIONS • Verbally speak the problem • Have you seen this problem in the past? • Have you read about or hear someone talk about this problem? • What are the symptoms?33 ERIKREAGAN • EECI
  • 34. NON EE TIPS • .htaccess • print_r() • var_dump() • debug_backtrace() • Xdebug for PHP34 ERIKREAGAN • EECI
  • 35. GETTING HELP • Seek help on EE forums or 3rd party support channel • Ask on twitter (with the #eecms hash, of course) • Consider sites like Stack Overflow for general PHP or server issues35 ERIKREAGAN • EECI
  • 36. WHAT NOT TO DO • Bug the first person you see on AIM/Skype/gTalk without trying things yourself • Complain on the EE forums without troubleshooting yourself • Complain on a 3rd party devs forums without troubleshooting yourself • Complain on twitter36 ERIKREAGAN • EECI
  • 37. focuslabllc.com/blog/troubleshooting-expressionengine37 ERIKREAGAN • EECI
  • 38. THANKS! @ErikReagan38 ERIKREAGAN • EECI

×