~/talk

Debugging WordPress

Talkat WordCamp Belfast 2018 · 2018-05-26..05-27· [wordpress]
links:none on file
slides:none on file

Start by reading server error logs and enable WordPress’ debug constants so you get traceable errors rather than a blank 500 page: set WP_DEBUG true, log to file with WP_DEBUG_LOG true and keep display off with WP_DEBUG_DISPLAY false; use SCRIPT_DEBUG to load non‑minified assets. Use WP‑CLI to deactivate plugins, list versions and pinpoint a broken plugin or theme. Check common causes (wrong siteurl/home, missing upload path, “headers already sent”) and enable PHP output buffering as a practical fix for stray output.

AI-written summary · about

  1. 0:00Introduction and setup
  2. 1:41Types of WordPress errors
  3. 3:13Debugging tools and logs
  4. 6:51WP debug configuration
  5. 7:42WP CLI for debugging
  6. 9:24Plugin compatibility checks
  7. 10:26Unexpected PHP results
  8. 11:53Disabling minified files
  9. 12:37Media library and URL issues
  10. 15:15Header output errors
  11. 18:19Future of WordPress debugging
  12. 20:19Reporting bugs effectively
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.