PHP Syntax Error in Setting Global Variable
Ok, so my PHP is, to say the least, horrible. I inherited an application and am having to fix errors in it from someone that wrote it over 7 years ago. When I run the page, there is no return, so I checked the logs to see the error and here is what i get:
PHP Parse error: syntax error, unexpected ‘=’, expecting ‘,’ or ‘;’ in /httpdocs/cron123/purge.php on line 4
purge(); new dBug($ftresult); echo "successfully wrote"; ?>
Best Solution
global is a keyword that should be used by itself. It must not be combined with an assignment. So, chop it:
Also, as Zenham mentions, global is used inside functions, to access variables in an outer scope. So the use of global as it is presented makes little sense.
Another tip (though it will not really help you with syntax errors): add the following line to the top of the main file, to help debugging (documentation):
Related Solutions
Php – How to prevent SQL injection in PHP
The correct way to avoid SQL injection attacks, no matter which database you use, is to separate the data from SQL, so that data stays data and will never be interpreted as commands by the SQL parser. It is possible to create SQL statement with correctly formatted data parts, but if you don’t fully understand the details, you should always use prepared statements and parameterized queries. These are SQL statements that are sent to and parsed by the database server separately from any parameters. This way it is impossible for an attacker to inject malicious SQL.
You basically have two options to achieve this:
- Using PDO (for any supported database driver):
$stmt = $pdo->prepare('SELECT * FROM employees WHERE name = :name'); $stmt->execute([ 'name' => $name ]); foreach ($stmt as $row) < // Do something with $row >
$stmt = $dbConnection->prepare('SELECT * FROM employees WHERE name = ?'); $stmt->bind_param('s', $name); // 's' specifies the variable type => 'string' $stmt->execute(); $result = $stmt->get_result(); while ($row = $result->fetch_assoc()) < // Do something with $row >
If you’re connecting to a database other than MySQL, there is a driver-specific second option that you can refer to (for example, pg_prepare() and pg_execute() for PostgreSQL). PDO is the universal option.
Correctly setting up the connection
Note that when using PDO to access a MySQL database real prepared statements are not used by default. To fix this you have to disable the emulation of prepared statements. An example of creating a connection using PDO is:
$dbConnection = new PDO('mysql:dbname=dbtest;host=127.0.0.1;charset=utf8', 'user', 'password'); $dbConnection->setAttribute(PDO::ATTR_EMULATE_PREPARES, false); $dbConnection->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
In the above example the error mode isn’t strictly necessary, but it is advised to add it. This way the script will not stop with a Fatal Error when something goes wrong. And it gives the developer the chance to catch any error(s) which are throw n as PDOException s.
What is mandatory, however, is the first setAttribute() line, which tells PDO to disable emulated prepared statements and use real prepared statements. This makes sure the statement and the values aren’t parsed by PHP before sending it to the MySQL server (giving a possible attacker no chance to inject malicious SQL).
Although you can set the charset in the options of the constructor, it’s important to note that ‘older’ versions of PHP (before 5.3.6) silently ignored the charset parameter in the DSN.
Explanation
The SQL statement you pass to prepare is parsed and compiled by the database server. By specifying parameters (either a ? or a named parameter like :name in the example above) you tell the database engine where you want to filter on. Then when you call execute , the prepared statement is combined with the parameter values you specify.
The important thing here is that the parameter values are combined with the compiled statement, not an SQL string. SQL injection works by tricking the script into including malicious strings when it creates SQL to send to the database. So by sending the actual SQL separately from the parameters, you limit the risk of ending up with something you didn’t intend.
Any parameters you send when using a prepared statement will just be treated as strings (although the database engine may do some optimization so parameters may end up as numbers too, of course). In the example above, if the $name variable contains ‘Sarah’; DELETE FROM employees the result would simply be a search for the string «‘Sarah’; DELETE FROM employees» , and you will not end up with an empty table.
Another benefit of using prepared statements is that if you execute the same statement many times in the same session it will only be parsed and compiled once, giving you some speed gains.
Oh, and since you asked about how to do it for an insert, here’s an example (using PDO):
$preparedStatement = $db->prepare('INSERT INTO table (column) VALUES (:column)'); $preparedStatement->execute([ 'column' => $unsafeValue ]);
Can prepared statements be used for dynamic queries?
While you can still use prepared statements for the query parameters, the structure of the dynamic query itself cannot be parametrized and certain query features cannot be parametrized.
For these specific scenarios, the best thing to do is use a whitelist filter that restricts the possible values.
// Value whitelist // $dir can only be 'DESC', otherwise it will be 'ASC' if (empty($dir) || $dir !== 'DESC')
Javascript – How to guarantee that the enums definition doesn’t change in JavaScript
Since 1.8.5 it’s possible to seal and freeze the object, so define the above as:
const DaysEnum = Object.freeze()
const DaysEnum = Object.freeze(DaysEnum)
However, this doesn’t prevent you from assigning an undesired value to a variable, which is often the main goal of enums:
let day = DaysEnum.tuesday day = 298832342 // goes through without any errors
One way to ensure a stronger degree of type safety (with enums or otherwise) is to use a tool like TypeScript or Flow.
Quotes aren’t needed but I kept them for consistency.
Related Question
Php global syntax error
To learn Laravel, Aomoto (https://www.amazon.co.jp/PHP%E3%83%95%E3%83%AC%E3%83%BC%E3%83%A0 % E3% 83% AF% E3% 83% BC% E3% 82% AF-Laravel% E5% 85% A5% E9% 96% 80-% E6% 8E% 8C% E7% 94% B0% E6% B4% A5% E8% 80% B6% E4% B9% 83/dp/4798052582).
The following error message occurred while learning to use multiple actions when using the controller in Chapter 2.
Error message
syntax error, unexpected 'global' (T_GLOBAL), expecting function (T_FUNCTION) or const (T_CONST)
<? php namespace App \ Http \ Controllers; use Illuminate \ Http \ Request; class HelloController extends Controller < global $head, $style, $body, $end; $head = '<html><head>'; $style =<<<EOF <style> body h1 </style> EOF; $body = '</head><body>'; $end = '</body></html>'; function tag ($tag, $txt) < return "<>". $txt. "</>"; > class HelloController extends Controller < public function index () < global $head, $style, $body, $end; $html = $head.tag ('title', 'Hello/Index'). $style. $body.tag ('h1', 'Index'). tag ('p', 'this is Index page'). '<a href = "/ hello/other">go to Other page</a>'. $end; return $html; >public function other () < global $head, $style, $body, $end; $html = $head.tag ('title', 'Hello/Other'). $style. $body.tag ('h1', 'Other'). tag ('p', 'this is Other page'). '<a href = "/ hello/other">go to Other page</a>'. $end; return $html; >> >
I tried to search for errors in Google, StackOverflow, etc.
I knew that the syntax error was a syntax error, and I knew that the information after that was a clue, but because I was copying the blue book, I wasn’t sure what was the problem at all.
Supplemental information (FW/tool version etc.)
namespace and use are simply omitted, so the class definition near the 7th line and the last parenthesis are unnecessary. The combination of double definition and the fact that global cannot be written in a class variable is a syntax error.
class HelloController extends Controller
'; $style = / * body and anything * / EOF; $body = ''; $end = ''; function tag ($tag, $txt) < return ">". $txt. ">"; > class HelloController extends Controller < public function index () < global $head, $style, $body, $end; $html = $head. tag ('title', 'Hello/Index'). $style. $body // hereafter omitted
You'll only use it for today's global or WordPress strange insertions, such as the Laravel book example.
I tried to buy it with interest, but I really wrote global.
A view file is fine, and if you give it a hundred steps and write to this file, it's a class variable This book has many page breaks in the middle of the code, but is it so even on paper media? The commentary doesn't look bad, but it seems better to readthe code in some strange places and some uses that are not actually used. The version is also 5.4 so it's a bit old.
Things to do throw the book away. Laravel can't be used globally, as it might be for beginners.
It is impossible for beginners who do not know if it is impossible to use Laravel, so learning from the basics of PHP is necessary.
You should check what is in the book.
Since it is strange overall, I think that the description in the question is not written in the book.
If you just fix it, I think it is possible to resolve the error by properly using the here document syntax.
If you are using an IDE, it is a syntax error that you can see before execution. However, it is certain that it is a book that should not be used very actively as already published, so please shift to at least a Japanese translation document.
Perhaps the environment including each version is not exactly the same.
Related articles
- php - [wordpress] about jquery errors
- php - about the multiple structure of laravel's many-to-many relations
- [php] about the relationship between the number of select statements and the reading speed
- about php zend framework flashmessenger
- php - please tell me how to resolve mysql errors wordpress "database connection establishment error"
- php parse error: syntax error, unexpected'class' (t_class) error
- python - about errors in google colaboratory
- php - laravel get information about the user who clicked
- php - about laravel's associative array
- (vuejs) about errors in the processing of methods
- php - about array curly braces
- python - about errors in deep learning
- php - about dockerfile
- c - i'm not sure about the inline assembly syntax and rules, so please
- php - about javascript document
- php - i don't know how to fix "syntax error" after changing wordpress and css
- php - about the speed of data transfer
- about php date function
- python - about errors when using the camera module of raspberry pie
- cakephp/crud: about query parameter value retrieval
PHP Syntax Error in Setting Global Variable
Ok, so my PHP is, to say the least, horrible. I inherited an application and am having to fix errors in it from someone that wrote it over 7 years ago. When I run the page, there is no return, so I checked the logs to see the error and here is what i get:
PHP Parse error: syntax error, unexpected '=', expecting ',' or ';' in /httpdocs/cron123/purge.php on line 4
purge(); new dBug($ftresult); echo "successfully wrote"; ?>
Russ Bradberry
3 Answers
global is a keyword that should be used by itself. It must not be combined with an assignment. So, chop it:
Also, as Zenham mentions, global is used inside functions, to access variables in an outer scope. So the use of global as it is presented makes little sense.
Another tip (though it will not really help you with syntax errors): add the following line to the top of the main file, to help debugging (documentation):
Stephan202
The global keyword is used inside of functions to declare that they will use a globally defined variable, not to define one. Just remove the word global, and if you need those values in functions, add:
. to the start to the function.
markh
See here. global is a modifier which means the variable comes from the global scope. It should just be
and in functions which use them (but you don't have any in this page)