Every WordPress user eventually finds a tutorial that says "just add this to your functions.php". It works, right up until the day it doesn't — and when PHP fails in functions.php, it usually takes the whole site down, admin panel included.
Here's why that happens, what to do instead, and how to get back in when you're already locked out.
Why functions.php is a trap
Three separate problems. First, a syntax error is fatal — one missing semicolon produces a white screen across the entire site, including /wp-admin, so you can't fix it through WordPress. Second, theme updates overwrite it, silently deleting months of accumulated snippets. Third, everything is entangled: twenty unrelated snippets in one file with no labels means that when something breaks, you have no idea which one did it.
Option 1: a child theme
A child theme inherits everything from the parent and holds your customisations separately, so parent updates no longer wipe them. This is the right answer for template changes and substantial theme work.
It doesn't solve the other two problems, though. A fatal error in a child theme's functions.php still takes the site down, and you still end up with one long unlabelled file.
Option 2: a snippet manager
A snippet plugin stores each piece of code as a separate, named, individually toggleable entry in the database. The advantages compound quickly:
- Each snippet can be switched off without touching the others.
- Snippets are named and described, so you know what each one does a year later.
- They survive theme changes entirely — switch themes and your code follows.
- Good managers validate syntax before saving, catching the fatal error rather than shipping it.
- You control where each runs: frontend only, admin only, or everywhere.
That last point matters more than it sounds. Code that only needs to run in the admin has no business executing on every visitor page load. Code Snippets Pro handles PHP, CSS, JavaScript, and HTML with conditional loading and per-snippet priority for exactly this reason.
Option 3: a site-specific plugin
For developers, a small custom plugin containing your functions is arguably cleanest — version-controlled, deployable, entirely independent of the theme. It's more setup than most site owners want, but it's the professional answer.
Where CSS actually belongs
Not in functions.php, and not in the theme's style.css if you're using a parent theme. Small tweaks go in Appearance → Customise → Additional CSS, which is update-safe and instantly reversible. Larger stylesheets belong in a child theme or a snippet manager's CSS section.
The rules that prevent most disasters
Back up before you paste. Not "have backups configured" — take one immediately before, so restoring costs minutes rather than a day of lost orders.
Add one snippet at a time and test. Pasting five at once means five suspects when something breaks.
Understand what it does first. If you can't explain roughly what a snippet does, don't run it. Random code from a forum can contain anything, and code that "adds a feature" while quietly phoning home is a real category of attack.
Never edit files on a live site with traffic. Use staging. Most decent hosts include it free.
Prefer hooks over core edits. If a tutorial tells you to edit a WordPress core file, close the tab. Core updates will overwrite it, and there is always a hook.
Recovering from a white screen
You pasted something, hit save, and the site is gone. Don't panic — this is recoverable and you have not lost your data.
Connect over FTP or your host's file manager, open the file you last edited, and remove what you added. The site comes back immediately. If you're not sure which file, rename your active theme's folder — WordPress falls back to a default theme, which usually restores admin access so you can work from inside.
To see the actual error rather than a blank page, set WP_DEBUG to true in wp-config.php temporarily. The error message names the file and line number, which turns guesswork into a two-minute fix. Turn it off afterwards — you don't want PHP errors visible to visitors.
The short version
Use a child theme for template work, a snippet manager for functional additions, the Customiser for small CSS, and take a backup before any of it. Do that and "add this to functions.php" stops being the sentence that ruins your afternoon.
