Fixing a PHP parse or syntax error after editing a theme

A PHP parse or syntax error means you edited a theme file (usually functions.php or a template file) and left something malformed: a missing semicolon, an unclosed brace, a stray quote. WordPress shows a message like "Parse error: syntax error, unexpected..." along with a file path and line number. Fix that exact line in that exact file and the site comes back immediately. No plugin, no database, no server issue involved.

This is different from the white screen of death, where PHP fails silently. A parse error is usually loud: it names the file and line. Treat this as the fast path, and only dig deeper if the error message doesn't point you anywhere useful.

Read the error message first

The message tells you almost everything. For example:

Parse error: syntax error, unexpected '}' in /home/youraccount/public_html/wp-content/themes/your-theme/functions.php on line 214

That's a file path and a line number. Open that file (via FTP or the portal's File Manager) and go straight to that line. The three most common causes on our stack, in order of frequency:

1. A missing or extra bracket, brace, or parenthesis

The error usually points a few lines after the actual mistake, because PHP doesn't realize something's wrong until it hits the next token that doesn't fit. If line 214 says unexpected '}', check the lines above it for a brace that was deleted, doubled, or misplaced when you pasted in a code snippet.

2. A missing semicolon or unclosed quote

Common when copy-pasting a snippet from a tutorial or forum post that got mangled by formatting (curly quotes instead of straight quotes are a frequent culprit). Look for a line ending in a value with no ;, or a string that opens with ' or " and never closes.

3. A stray closing PHP tag or extra whitespace

If you edited functions.php and it now ends with ?> followed by a blank line or space, that alone can break things once WordPress tries to send headers later. The safe convention is to leave off the closing ?> tag entirely in files that don't mix PHP and HTML output.

Fix it directly

1. Open the file named in the error via FTP or File Manager.
2. Go to the line number given (or a few lines above it if nothing looks wrong at that exact line).
3. Correct the syntax: add the missing semicolon, close the bracket, fix the quote.
4. Save and reload the site.

If you don't trust your fix, or the error message isn't specific enough to find the problem, the faster move is to revert: replace the file with the version you had before you started editing. If you don't have a backup of the single file, restore from a full backup via the portal's Backups tile, then reapply your change more carefully, one edit at a time.

If you can't find the file, or it's not your edit

Sometimes the parse error shows up after a plugin or theme update, not a manual edit, usually because an update was interrupted or a file got corrupted mid-transfer. In that case:

• Re-upload the theme or plugin fresh via FTP, overwriting the broken files.
• If it's a child theme causing the trouble rather than the parent, see child themes: why your edits keep disappearing for how the two relate, since a bad edit to a child theme's functions.php is a common source of exactly this error.
• Check your PHP version if the code you added uses newer syntax (like named arguments or enums) than the theme's minimum supports. Switch versions from Services → your hosting → the PHP Version tile to test.

Once the site loads again, if you're doing more theme customization going forward, read updating WordPress safely for the backup-first habit that makes these edits low-risk: back up before you touch a file, so a bad edit is a one-click revert instead of a scramble.

When to open a ticket

Paste the exact error text and mention what you changed and when. Support can look at the file directly. If you're locked out of FTP or File Manager because the error is blocking a redirect loop, mention that too.