Синтаксическая ошибка незавершенный список параметров

What are the syntax errors?

PHP belongs to the C-style and imperative 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.

Most important tips

There are a few basic precautions you can always take:

• Use proper code indentation, or adopt any lofty coding style.
  Readability prevents irregularities.

• Use an IDE or editor for PHP with syntax highlighting.
  Which also help with parentheses/bracket balancing.

  

• Read the language reference and examples in the manual.
  Twice, to become somewhat proficient.

How to interpret parser errors

A typical syntax error message reads:

Parse error: syntax error, unexpected T_STRING, expecting ‘;‘ in file.php on line 217

Which lists the possible location of a syntax mistake. See the mentioned file name and line number.

A moniker such as T_STRING explains which symbol the parser/tokenizer couldn’t process finally. This isn’t necessarily the cause of the syntax mistake, however.

It’s important to look into previous code lines 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.

Solving syntax errors

There are many approaches to narrow down and fix syntax hiccups.

• Open the mentioned source file. Look at the mentioned code line.

  • For runaway strings and misplaced operators, this is usually where you find the culprit.

  • Read the line left to right and imagine what each symbol does.

• More regularly you need to look at preceding lines as well.

  • In particular, missing ; semicolons are missing at the previous line ends/statement. (At least from the stylistic viewpoint. )

  • If { code blocks } are incorrectly closed or nested, you may need to investigate even further up the source code. Use proper code indentation to simplify that.

• Look at the syntax colorization!

  • Strings and variables and constants should all have different colors.

  • Operators +-*/. should be tinted distinct as well. Else they might be in the wrong context.

  • If you see string colorization extend too far or too short, then you have found an unescaped or missing closing " or ' string marker.

  • Having two same-colored punctuation characters next to each other can also mean trouble. Usually, operators are lone if it’s not ++, --, or parentheses following an operator. Two strings/identifiers directly following each other are incorrect in most contexts.

• Whitespace is your friend.
  Follow any coding style.

• Break up long lines temporarily.

  • You can freely add newlines 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.

  • Split up complex if statements into distinct or nested if conditions.

  • Instead of lengthy math formulas or logic chains, use temporary variables to simplify the code. (More readable = fewer errors.)

  • Add newlines between:

    1. The code you can easily identify as correct,
    2. The parts you’re unsure about,
    3. And the lines which the parser complains about.

    Partitioning up long code blocks really helps to locate the origin of syntax errors.

• Comment out offending code.

  • If you can’t isolate the problem source, start to comment out (and thus temporarily remove) blocks of code.

  • As soon as you got rid of the parsing error, you have found the problem source. Look more closely there.

  • Sometimes you want to temporarily remove complete function/method blocks. (In case of unmatched curly braces and wrongly indented code.)

  • When you can’t resolve the syntax issue, try to rewrite the commented out sections from scratch.

• As a newcomer, avoid some of the confusing syntax constructs.

  • The ternary ? : condition operator can compact code and is useful indeed. But it doesn’t aid readability in all cases. Prefer plain if statements while unversed.

  • PHP’s alternative syntax (if:/elseif:/endif;) is common for templates, but arguably less easy to follow than normal { code } blocks.

• The most prevalent newcomer mistakes are:

  • Missing semicolons ; for terminating statements/lines.

  • Mismatched string quotes for " or ' and unescaped quotes within.

  • Forgotten operators, in particular for the string . concatenation.

  • Unbalanced ( parentheses ). Count them in the reported line. Are there an equal number of them?

• Don’t forget that solving one syntax problem can uncover the next.

  • If you make one issue go away, but other crops up in some code below, you’re mostly on the right path.

  • If after editing a new syntax error crops up in the same line, then your attempted change was possibly a failure. (Not always though.)

• Restore a backup of previously working code, if you can’t fix it.

  • Adopt a source code versioning system. You can always view a diff of the broken and last working version. Which might be enlightening as to what the syntax problem is.
    

• Invisible stray Unicode characters: 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.

  • Try grep --color -P -n "[x80-xFF]" file.php as the first measure to find non-ASCII symbols.

  • In particular BOMs, zero-width spaces, or non-breaking spaces, and smart quotes regularly can find their way into the source code.

• Take care of which type of linebreaks are saved in files.

  • PHP just honors n newlines, not r carriage returns.

  • Which is occasionally an issue for MacOS users (even on OS  X for misconfigured editors).

  • It often only surfaces as an issue when single-line // or # comments are used. Multiline /*...*/ comments do seldom disturb the parser when linebreaks get ignored.

• If your syntax error does not transmit over the web:
  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:

  • You are looking at the wrong file!

  • Or your code contained invisible stray Unicode (see above).
    You can easily find out: Just copy your code back from the web form into your text editor.

• Check your PHP version. Not all syntax constructs are available on every server.

  • php -v for the command line interpreter

  • <?php phpinfo(); for the one invoked through the webserver.

  Those aren’t necessarily the same. In particular when working with frameworks, you will them to match up.

• Don’t use PHP’s reserved keywords as identifiers for functions/methods, classes or constants.

• Trial-and-error is your last resort.

If all else fails, you can always google your error message. Syntax symbols aren’t as easy to search for (Stack Overflow itself is indexed by SymbolHound though). Therefore it may take looking through a few more pages before you find something relevant.

Further guides:

• PHP Debugging Basics by David Sklar
• Fixing PHP Errors by Jason McCreary
• PHP Errors – 10 Common Mistakes by Mario Lurig
• Common PHP Errors and Solutions
• How to Troubleshoot and Fix your WordPress Website
• A Guide To PHP Error Messages For Designers — Smashing Magazine

White screen of death

If your website is just blank, then typically a syntax error is the cause.
Enable their display with:

• error_reporting = E_ALL
• display_errors = 1

In your php.ini generally, or via .htaccess for mod_php,
or even .user.ini with FastCGI setups.

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 test.php:

<?php
   error_reporting(E_ALL);
   ini_set("display_errors", 1);
   include("./broken-script.php");

Then invoke the failing code by accessing this wrapper script.

It also helps to enable PHP’s error_log and look into your webserver’s error.log when a script crashes with HTTP 500 responses.