PHP Syntax Debugging Reference Information

This error renders when a script exceeds the default "memory_limit" setting inside your PHP configuration file(php.ini) on your server. Best practice is to always make more efficient programs instead of maxing out the PHP memory limited allocated. If you must allow a beefy memory hog file to run you can check the fix suggestions below. You may have to restart Apache to have any php.ini changes take place, especially on local PHP environments.

This error will render when you call a function to run that does not exist to the script, or you are not using the proper case when calling the function.

When working with classes in PHP it often renders when you forget to place "$this->" when refering to on object.

This error usually renders when a coder working with PHP classes forgets to define an object correctly in their calling script, then attempts to access that object's methods. It can also render when you forget to place "$this->" when refering to on object and its methods.

This error usually means that you are trying to declare a function or class that has already been declared in your script.

This error renders when a script exceeds the default "memory_limit" setting inside your PHP configuration file(php.ini) on your server. Best practice is to always make more efficient scripts instead of maxing out the PHP memory limited allocated. If you must allow a beefy memory hog file to run you can check the fix suggestions below. You may have to restart Apache to have any php.ini changes take place, especially on local PHP environments.

This notice means that a global variable or database table field has not been set in your PHP before you attempted to script with it. Meaning you have to see first if that variable is set or ready for use in the script. If you are building a form all you have to do is see that one of the form's $_POST variables isset() before gathering the variables up into local PHP variables. Simply trying to place a $_POST[''] type variable in your script without seeing if it is set first, will render this Notice in many PHP environments. Some environments will not render this error depending on the PHP configuration on the server.

This notice means that a variable that is in place for output or manipulation in your script has not been initialized or defined prior to using it.

When you see the "unexpected $end" syntax error it is telling you that you left something open that should have closed(usually improper curly bracket or quote nesting). This error is many times difficult to pinpoint in your script because the error line that is returned is not going to be the line where the nest opens. The error line is usually where the program ends. Functions, loops, condition statements, as well as other mechanisms use curly brackets to open and close those mechanisms ( { } ). Strings will use quote marks for encapsulation and nesting. This error will also render when you use short opening PHP tags(<?) instead of the normal(<?php). To use short PHP tags you must configure your php.ini file to make them work.

This notice usually renders when you begin the name of a function with a number.

This notice will render when you begin the name of a variable with a number.

This warning will usually appear when the fields you are claiming in your SQL syntax do not exist in your database table.

This warning will usually appear when the fields you are claiming in your SQL syntax do not exist in your database table.

This warning will appear when you do not place a parameter in the mysqli_error() function. It is looking for a link identifier returned by either mysqli_connect() or mysqli_init().

SQL syntax is separate from PHP syntax. It is the string of text used inside of your mysql_query() functions. The many ways you can cause errors in your SQL syntax cannot reasonably be listed here. Best bet it to learn raw SQL syntax apart from how it applies to PHP, and then learn the many ways PHP communicates to your MySQL database.