What are the syntax errors?<\/h3>\n
PHP belongs to the C-style<\/a> and imperative<\/a> programming languages. It has rigid grammar rules, which it cannot recover from when encountering misplaced symbols or identifiers. It can’t guess your coding intentions.<\/p>\n There are a few basic precautions you can always take:<\/p>\n Use proper code indentation<\/strong>, or adopt any lofty coding style. Use an IDE<\/em><\/strong> or editor for PHP<\/a> with syntax highlighting<\/strong>. Read the language reference<\/a> and examples in the manual. A typical syntax error message reads:<\/p>\n Parse error: syntax error, unexpected T_STRING<\/strong>, expecting ‘ Which lists the possible<\/em> location of a syntax mistake. See the mentioned file name<\/strong> and line number<\/strong>.<\/p>\n A moniker<\/a> such as It’s important to look into previous code lines<\/strong> as well. Often syntax errors are just mishaps that happened earlier. The error line number is just where the parser conclusively gave up to process it all.<\/p>\n There are many approaches to narrow down and fix syntax hiccups.<\/p>\n Open the mentioned source file. Look at the mentioned code line<\/strong>.<\/p>\n For runaway strings and misplaced operators, this is usually where you find the culprit.<\/p>\n<\/li>\n Read the line left to right and imagine what each symbol does.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n More regularly you need to look at preceding lines<\/strong> as well.<\/p>\n In particular, missing If Look at the syntax colorization<\/strong>!<\/p>\n Strings and variables and constants should all have different colors.<\/p>\n<\/li>\n Operators If you see string colorization extend too far or too short, then you have found an unescaped or missing closing Having two same-colored punctuation characters next to each other can also mean trouble. Usually, operators are lone if it’s not Whitespace is your friend<\/strong>. Break up long lines temporarily.<\/p>\n You can freely add newlines<\/strong> between operators or constants and strings. The parser will then concretize the line number for parsing errors. Instead of looking at the very lengthy code, you can isolate the missing or misplaced syntax symbol.<\/p>\n<\/li>\n Split up complex Instead of lengthy math formulas or logic chains, use temporary variables to simplify the code. (More readable = fewer errors.)<\/p>\n<\/li>\n Add newlines between:<\/p>\n Partitioning up long code blocks really<\/em> helps to locate the origin of syntax errors.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Comment out<\/strong> offending code.<\/p>\n If you can’t isolate the problem source, start to comment out (and thus temporarily remove) blocks of code.<\/p>\n<\/li>\n As soon as you got rid of the parsing error, you have found the problem source. Look more closely there.<\/p>\n<\/li>\n Sometimes you want to temporarily remove complete function\/method blocks. (In case of unmatched curly braces and wrongly indented code.)<\/p>\n<\/li>\n When you can’t resolve the syntax issue, try to rewrite<\/strong> the commented out sections from scratch<\/strong>.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n As a newcomer, avoid some of the confusing syntax constructs.<\/p>\n The ternary PHP’s alternative syntax ( The most prevalent newcomer mistakes are:<\/p>\n Missing semicolons Mismatched string quotes for Forgotten operators, in particular for the string Unbalanced Don’t forget that solving one syntax problem can uncover the next.<\/p>\n If you make one issue go away, but other crops up in some code below, you’re mostly on the right path.<\/p>\n<\/li>\n If after editing a new syntax error crops up in the same line, then your attempted change was possibly a failure. (Not always though.)<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Restore a backup of previously working code, if you can’t fix it.<\/p>\n Invisible stray Unicode characters<\/strong>: In some cases, you need to use a hexeditor or different editor\/viewer on your source. Some problems cannot be found just from looking at your code.<\/p>\n Try In particular BOMs, zero-width spaces, or non-breaking spaces, and smart quotes regularly can find their way into the source code.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Take care of which type of linebreaks<\/strong> are saved in files.<\/p>\n PHP just honors \\n<\/kbd> newlines, not \\r<\/kbd> carriage returns.<\/p>\n<\/li>\n Which is occasionally an issue for MacOS users (even on OS\u00a0 X for misconfigured editors).<\/p>\n<\/li>\n It often only surfaces as an issue when single-line If your syntax error does not transmit over the web<\/strong>: You are looking at the wrong file!<\/p>\n<\/li>\n Or your code contained invisible stray Unicode (see above). Check your PHP version<\/strong>. Not all syntax constructs are available on every server.<\/p>\n Those aren’t necessarily the same. In particular when working with frameworks, you will them to match up.<\/p>\n<\/li>\n Don’t use PHP’s reserved keywords<\/a> as identifiers for functions\/methods, classes or constants.<\/p>\n<\/li>\n Trial-and-error is your last resort.<\/p>\n<\/li>\n<\/ul>\n If all else fails, you can always google<\/strong> your error message. Syntax symbols aren’t as easy to search for (Stack Overflow itself is indexed by SymbolHound<\/a> though). Therefore it may take looking through a few more pages before you find something relevant.<\/p>\n Further guides:<\/p>\n If your website is just blank, then typically a syntax error is the cause. In your Enabling it within the broken script is too late because PHP can’t even interpret\/run the first line. A quick workaround is crafting a wrapper script, say Then invoke the failing code by accessing this wrapper script.<\/p>\n It also helps to enable PHP’s ![\"Function](\"https:\/\/jassweb.com\/solved\/wp-content\/uploads\/2022\/08\/Solved-PHP-parsesyntax-errors-and-how-to-solve-them.gif\")
<\/p>\nMost important tips<\/h3>\n
\n
\nReadability prevents irregularities.<\/p>\n<\/li>\n
\nWhich also help with parentheses\/bracket balancing.<\/p>\n![\"Expected:](\"https:\/\/jassweb.com\/solved\/wp-content\/uploads\/2022\/08\/Solved-PHP-parsesyntax-errors-and-how-to-solve-them.png\")
<\/p>\n<\/li>\n
\nTwice, to become somewhat proficient.<\/p>\n<\/li>\n<\/ul>\nHow to interpret parser errors<\/h3>\n
\n
;<\/code>‘<\/strong> in file.php<\/em> on line<\/strong> 217<\/em><\/p>\n<\/blockquote>\nT_STRING<\/code> explains which symbol the parser\/tokenizer couldn’t process finally. This isn’t necessarily the cause of the syntax mistake, however.<\/p>\nSolving syntax errors<\/h2>\n
\n
\n
\n
;<\/code> semicolons are missing at the previous line ends\/statement. (At least from the stylistic viewpoint. )<\/p>\n<\/li>\n{<\/code> code blocks }<\/code> are incorrectly closed or nested, you may need to investigate even further up the source code. Use proper code indentation<\/em> to simplify that.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\n
+-*\/.<\/code> should be tinted distinct as well. Else they might be in the wrong context.<\/p>\n<\/li>\n\"<\/code> or '<\/code> string marker.<\/p>\n<\/li>\n++<\/code>, --<\/code>, or parentheses following an operator. Two strings\/identifiers directly following each other are incorrect in most contexts.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
\n Follow any<\/em> coding style.\n <\/p>\n<\/li>\n\n
if<\/code> statements into distinct or nested if<\/code> conditions.<\/p>\n<\/li>\n\n
\n
\n
? :<\/code> condition operator can compact code and is useful indeed. But it doesn’t aid readability in all cases. Prefer plain if<\/code> statements while unversed.<\/p>\n<\/li>\nif:<\/code>\/elseif:<\/code>\/endif;<\/code>) is common for templates, but arguably less easy to follow than normal {<\/code> code }<\/code> blocks.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\n
;<\/code> for terminating statements\/lines.<\/p>\n<\/li>\n\"<\/code> or '<\/code> and unescaped quotes within.<\/p>\n<\/li>\n.<\/code> concatenation.<\/p>\n<\/li>\n(<\/code> parentheses )<\/code>. Count them in the reported line. Are there an equal number of them?<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\n
\n
diff<\/code> of the broken and last working version. Which might be enlightening as to what the syntax problem is.
\n<\/li>\n<\/ul>\n<\/li>\n\n
grep --color -P -n \"\\[\\x80-\\xFF\\]\" file.php<\/code> as the first measure to find non-ASCII symbols.<\/p>\n<\/li>\n\n
\/\/<\/code> or #<\/code> comments are used. Multiline \/*...*\/<\/code> comments do seldom disturb the parser when linebreaks get ignored.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
\n It happens that you have a syntax error on your machine. But posting the very same file online does not exhibit it anymore. Which can only mean one of two things:<\/p>\n\n
\nYou can easily find out: Just copy your code back from the web form into your text editor.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n\n
php -v<\/code> for the command line interpreter<\/p>\n<\/li>\n<?php phpinfo();<\/code> for the one invoked through the webserver.<\/p>\n<\/li>\n<\/ul>\n\n
White screen of death<\/h3>\n
\nEnable their display with:<\/p>\n\n
error_reporting = E_ALL<\/code><\/li>\ndisplay_errors = 1<\/code><\/li>\n<\/ul>\nphp.ini<\/code><\/a> generally, or via .htaccess<\/code><\/a> for mod_php,
\nor even .user.ini<\/code><\/a> with FastCGI setups.<\/p>\ntest.php<\/code>:<\/p>\n<?php\n error_reporting(E_ALL);\n ini_set(\"display_errors\", 1);\n include(\".\/broken-script.php\");\n<\/code><\/pre>\nerror_log<\/code> and look into your webserver’s error.log<\/code><\/a> when a script crashes with HTTP 500 responses.<\/p>\n<\/p><\/div>\n