How To Fix Syntax Error In WordPress

The error message tells you exactly which file to open. You have two options for accessing it remotely:

• FTP client: Download and install FileZilla (free). Connect using the FTP credentials from your hosting account’s control panel. Look for a section called “FTP Accounts” or “File Manager.” Navigate to the path shown in the error message. An error in /wp-content/themes/yourtheme/functions.php means the theme folder inside your WordPress installation.
• Hosting file manager: Most hosts (cPanel, Plesk, Cloudways) include a browser-based file manager. Log into your hosting dashboard, open File Manager, and navigate to your WordPress files. This avoids installing FTP software and works on any device with a browser.

Download the file to your computer and open it in a text editor. The right editor makes this much easier:

• VS Code (recommended, free): Microsoft’s free code editor highlights PHP syntax and flags errors directly in the file. It often shows a red underline at the exact problem before you even search for it.
• Notepad++ (Windows, free): Color-codes PHP syntax and displays line numbers in the left margin. Press Ctrl+G to jump directly to a line number.
• Notepad (basic): Works as a last resort. Go to Edit > Go To to jump to a specific line number.

Do not open PHP files in Microsoft Word or Google Docs. Word processors silently add invisible formatting characters that introduce new errors when you save.

Use the keyboard shortcut to jump directly to the line number from the error message:

• VS Code: Press Ctrl+G (Windows/Linux) or Cmd+G (Mac), type the line number, press Enter.
• Notepad++: Press Ctrl+G, enter the line number.
• Notepad: Click Edit > Go To, enter the line number.

One important thing to know: PHP reports the line where it noticed the problem, which is often one or two lines after the actual mistake. For example, a missing semicolon on line 430 might not be flagged until PHP reaches line 432 and sees the next statement. If nothing on the reported line looks wrong, check the lines immediately above it.

The most common PHP syntax errors in WordPress files:

• Missing semicolon: Every PHP statement must end with a semicolon. echo 'hello' causes a parse error; echo 'hello'; does not. Look for a line that ends without one.
• Unclosed string: A text string that opens with a quote but never closes. For example, $text = 'Welcome to my site; (the closing apostrophe was accidentally deleted). The file looks normal at a glance but PHP cannot find the end of the string.
• Mismatched bracket or brace: A function or if-statement that opens { but never closes with }, or vice versa. This is common when pasting code snippets that are missing context.
• Curly quotes instead of straight quotes: Content copied from a Word document, PDF, or some blog posts contains typographic “smart quotes” instead of straight quotes. PHP does not recognize curly quotes and throws an immediate parse error.

Once you find the error, fix it, save the file, and reupload it to the same location using your FTP client or file manager, overwriting the original.

Reload your site in a browser. If the fix was correct, the error screen disappears and the site loads normally.

If problems persist:

• Error message unchanged: The file upload may not have completed. Check your FTP client for a failed transfer, then try uploading again.
• Blank white screen instead of error: You introduced a new error while editing. Go back to the file and recheck the line you changed.
• Different line number now: A second syntax error was hidden behind the first one. PHP stops at the first error it finds. Fix each one in order until the site loads.

If the syntax error appeared immediately after installing or updating a plugin or theme, disabling it is the fastest fix:

• If you can access wp-admin: Go to Plugins, find the plugin, and click Deactivate. For a theme, go to Appearance > Themes and switch to a default theme like Twenty Twenty-Four.
• If you are locked out of wp-admin: Use your FTP client or file manager to rename the plugin’s folder. WordPress automatically deactivates any plugin it cannot find. For example, rename wp-content/plugins/problem-plugin/ to wp-content/plugins/problem-plugin-disabled/. Once your site is accessible again, rename it back.

After disabling the plugin, contact the developer with the exact error message and the line number. Most developers release a patch within a day or two. If you need the plugin active immediately, check the WordPress plugin repository for an older version to downgrade to as a temporary fix.