Fatal error uncaught error call to a member function setpageproperty

Bug report

just ran into a «random» error, which phpstan told me to open a issue with this stack trace:

phpstan analyse -c phpstan.neon.dist
 252/252 [============================] 100% ------ --------------------------------------------------------------
  Line   libDebug.php
 ------ --------------------------------------------------------------
         Internal error: Call to a member function getType() on null
         Run PHPStan with --debug option and post the stack trace to:
         https://github.com/phpstan/phpstan/issues/new
 ------ --------------------------------------------------------------

so, running with --debug gets me:

PHP Fatal error:  Uncaught Error: Call to a member function getType() on null in phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Rules/Functions/IncompatibleDefaultParameterTypeRule.php:51
Stack trace:
#0 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/FileAnalyser.php(69): PHPStanRulesFunctionsIncompatibleDefaultParameterTypeRule->processNode(Object(PhpParserNodeStmtFunction_), Object(PHPStanAnalyserMutatingScope))
#1 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/NodeScopeResolver.php(243): PHPStanAnalyserFileAnalyser->PHPStanAnalyser{closure}(Object(PhpParserNodeStmtFunction_), Object(PHPStanAnalyserMutatingScope))
#2 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/NodeScopeResolver.php(203): PHPStanAnalyserNodeScopeResolver->processStmtNode(Object(PhpPa in phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Rules/Functions/IncompatibleDefaultParameterTypeRule.php on line 51
Fatal error: Uncaught Error: Call to a member function getType() on null in phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Rules/Functions/IncompatibleDefaultParameterTypeRule.php:51
Stack trace:
#0 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/FileAnalyser.php(69): PHPStanRulesFunctionsIncompatibleDefaultParameterTypeRule->processNode(Object(PhpParserNodeStmtFunction_), Object(PHPStanAnalyserMutatingScope))
#1 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/NodeScopeResolver.php(243): PHPStanAnalyserFileAnalyser->PHPStanAnalyser{closure}(Object(PhpParserNodeStmtFunction_), Object(PHPStanAnalyserMutatingScope))
#2 phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Analyser/NodeScopeResolver.php(203): PHPStanAnalyserNodeScopeResolver->processStmtNode(Object(PhpPa in phar://C:/Users/mstaab/Documents/GitHub/php-rocket/vendor-bin/phpstan/vendor/phpstan/phpstan/phpstan/src/Rules/Functions/IncompatibleDefaultParameterTypeRule.php on line 51
Script phpstan analyse -c phpstan.neon.dist --debug handling the phpstan event returned with error code 255

do you need more to reproduce or similar?

env:

$ php -v
PHP 7.4.5 (cli) (built: Apr 14 2020 16:17:19) ( NTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies

mstaab@NB-COMPLEX-15 MINGW64 ~/Documents/GitHub/php-rocket (rm-pear)
$ vendor/bin/phpstan -v
PHPStan - PHP Static Analysis Tool 0.12.25

  John Mwaniki /   18 Jan 2022

A prepared statement is a very useful feature in database management that increases efficiency and protects the database against SQL injections. It is also referred to as a parameterized statement.

It works by separating the SQL code from the data.

In the prepared statement, an SQL statement template is created and sent to the database with values unspecified (labeled with «?»). These question marks (?) are referred to as parameters.

The database parses, compiles, and performs query optimization on the SQL statement template, and stores the result without executing it.

The application later binds the values to the parameters, then executes the SQL statement. The application can execute the statement many times with different values without having to do the parsing and thus increasing the efficiency.

Since the parameter values are transmitted later, separately from the SQL statement using a different protocol, SQL injection cannot occur.

Below is an example code of inserting data in a table with a prepared statement in MySQLi.

<?php
$fname = "John"
$lname = "Doe";
$email = "johndoe@gmail.com";
$con = new mysqli("servername", "db_username", "db_password", "db_name");
$stmt = $con->prepare("INSERT INTO users(first_name, last_name, email) VALUES(?,?,?)");
$stmt->bind_param("sss", $fname, $lname, $email);
$stmt->execute();

The example below shows a code for updating a record in the database table using a prepared statement.

<?php
$fname = "John"
$lname = "Doe";
$email = "johndoe@gmail.com";
$userid = 5;
$con = new mysqli("servername", "db_username", "db_password", "db_name");
$stmt = $con->prepare("UPDATE users SET first_name = ?, last_name = ?, email = ? WHERE id = ?");
$stmt->bind_param("sssi", $fname, $lname, $email, $userid);
$stmt->execute();

When working with prepared statements in MySQLi, it’s common to encounter the error below from time to time.

PHP Fatal error: Uncaught Error: Call to a member function bind_param() on bool in /path/to/file/filename.php:x

This happens when prepare returns a bool false instead of a MySQLi statement object. That is then causing the fatal error you see here. This is due to an error in the SQL statement.

How to Fix the Error

Below are possible ways to fix the error:

• Countercheck to make sure that the name of the table and its columns which are specified in the SQL statement is exactly the same as in the database with no misspellings.
• If you specify the table columns you are working with, ensure that the number of column names matches that of the parameters (?). For instance in example 1 above, we have 3 columns (first_name, last_name, email) we are inserting into. We must include exactly 3 «?» and not more or less. Ensure that they are separated with commas (,) and no extra comma is there.
• If you don’t specify the column names that you’re inserting values into, then you have to give values for every column. For instance, if your table has 5 columns and you don’t specify columns in the statement, you have to supply 5 values or else you get the error.
• In the bind_param() function, make sure that the number of values is equal to the number of parameters (?) passed in the prepare() function. For instance, in example 1 we have 3 parameters (?,?,?) in the prepare() function and 3 values ($fname, $lname, $email) in the bind_param().
• Make sure to specify the types of data of the parameters as the first argument in the bind_param() function, eg «sss» in example 1 and «sssi» in example 2. The «s» character tells mysql that the parameter is a string. Other types include «i» for integer, «d» for double and «b» for BLOB.
  The number of types in the argument should be equal to the number of values. Their order should also be the same as that of the respective values.

By fixing any of the above possible causes, your code should definitely work with no errors.

2 hours ago, dunno said:

But your solution makes total sense: the global scope within the class must be inside the class but outside any function, and the call to that property within a function must be accessed using the «$this» keyword. A simple error which I will not forget. Thank you for pointing it out.

That is not quite an accurate description.

PHP has exactly two variable scopes: one for inside of functions (each function gets its own and it isn’t shared with other functions) and one for outside of functions (normally referred to as the global scope, which is the same everywhere and even shared across files).

<?php

$a = 1; // global scope
echo $a; // 1

function one() {
  echo $a; // empty: $a from the global scope is not available inside this function scope so this "$a" is different
  $a = 2; // a new variable in the function scope
  echo $a; // 2
}
one();

function two() {
  echo $a; // $a from the global scope or one's scope is not available inside here either
  $a = 3; // a new variable
  echo $a; // 3
}
two();

one(); // will output the same thing as before: first echo shows nothing, second echo shows 2

echo $a; // still 1

Code in functions can use the «global» keyword to access the global scope, but this is very strongly discouraged.

With classes, their functions («methods») have a function scope just like every other regular function has. What PHP does differently is give you a «$this» variable corresponding to the instance of the class. $this->db is using the $this variable (scoped only to the method) to access its «db» property (which has nothing to do with scope).

<?php

class Example {
  public $a;
  
  public function one() {
    echo $this->a;
    $this->a = 1;
    echo $this->a;
  }
  
  public function two() {
    echo $this->a;
  }
}

$example = new Example();
$example->one(); // first echo shows nothing because $a is undefined, second shows 1
$example->two(); // also 1

// echo $this->a; // "$this" is only available inside class methods

$example->a = 2;
$example->two(); // 2

Variable scope only matters for variables, as in things that use dollar signs, and besides the «public $a» (whose dollar sign is really more about the syntax for defining «a» in the Example class), there are only two ways that dollar signs are used in the above code: with $this and with $example.