这是什么?
这是一些关于在编程PHP时可能遇到的警告、错误和注意事项的答案,而不知道如何修复它们。这也是一个社区维基,所以每个人都被邀请加入和维护这个列表。
为什么会这样?
Questions like "Headers already sent" or "Calling a member of a non-object" pop up frequently on Stack Overflow. The root cause of those questions is always the same. So the answers to those questions typically repeat them and then show the OP which line to change in their particular case. These answers do not add any value to the site because they only apply to the OP's particular code. Other users having the same error cannot easily read the solution out of it because they are too localized. That is sad because once you understood the root cause, fixing the error is trivial. Hence, this list tries to explain the solution in a general way to apply.
我该怎么做呢?
如果您的问题被标记为此问题的副本,请在下面找到您的错误消息并将修复应用于您的代码。答案通常包含进一步的调查链接,以防仅从一般答案中不清楚。
如果您想投稿,请添加您“最喜欢的”错误消息、警告或通知,每个答案一条,简短描述它的含义(即使它只是突出显示手册页的术语),可能的解决方案或调试方法,以及现有的有价值的问答列表。此外,请随意改进任何现有的答案。
列表
Nothing is seen. The page is empty and white. (also known as White Page/Screen Of Death)
Code doesn't run/what looks like parts of my PHP code are output
Warning: Cannot modify header information - headers already sent
Warning: mysql_fetch_array() expects parameter 1 to be resource, boolean given a.k.a.
Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource
Warning: [function] expects parameter 1 to be resource, boolean given
Warning: [function]: failed to open stream: [reason]
Warning: open_basedir restriction in effect
Warning: Division by zero
Warning: Illegal string offset 'XXX'
Warning: count(): Parameter must be an array or an object that implements Countable
Parse error: syntax error, unexpected '['
Parse error: syntax error, unexpected T_XXX
Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE
Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM
Parse error: syntax error, unexpected 'require_once' (T_REQUIRE_ONCE), expecting function (T_FUNCTION)
Parse error: syntax error, unexpected T_VARIABLE
Fatal error: Allowed memory size of XXX bytes exhausted (tried to allocate XXX bytes)
Fatal error: Maximum execution time of XX seconds exceeded
Fatal error: Call to a member function ... on a non-object or null
Fatal Error: Call to Undefined function XXX
Fatal Error: Cannot redeclare XXX
Fatal error: Can't use function return value in write context
Fatal error: Declaration of AAA::BBB() must be compatible with that of CCC::BBB()'
Return type of AAA::BBB() should either be compatible with CCC::BBB(), or the #[\ReturnTypeWillChange] attribute should be used
Fatal error: Using $this when not in object context
Fatal error: Object of class Closure could not be converted to string
Fatal error: Undefined class constant
Fatal error: Uncaught TypeError: Argument #n must be of type x, y given
Notice: Array to string conversion (< PHP 8.0) or Warning: Array to string conversion (>= PHP 8.0)
Notice: Trying to get property of non-object error
Notice: Undefined variable or property
"Notice: Undefined Index", or "Warning: Undefined array key"
Notice: Undefined offset XXX [Reference]
Notice: Uninitialized string offset: XXX
Notice: Use of undefined constant XXX - assumed 'XXX' / Error: Undefined constant XXX
MySQL: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ... at line ...
Strict Standards: Non-static method [<class>::<method>] should not be called statically
Warning: function expects parameter X to be boolean/string/integer
HTTP Error 500 - Internal server error
Deprecated: Arrays and strings offset access syntax with curly braces is deprecated
还看到:
这个符号在PHP中是什么意思?
HTTP错误500 -内部服务器错误
HTTP状态代码500和典型的Apache或浏览器警告是一个非常广泛的消息。这不是实际的错误。要弄清楚是web服务器配置错误(.htaccess)还是PHP致命错误,你必须查看error.log。
你通常可以在下面找到webservers日志:
/var/log/apache2 on Linux servers, often used for local and virtual hosts.
/var/www/_user12345_/logs or similar on shared hosting plans.
Usually there's a logs/ directory alongside each htdocs/ folder.
C:\xampp\apache\logs\error.log for WAMP/XAMPP distributions of Apache+PHP.
Alternatively just use a file search feature to locate anything called "error.log".
Or look into your Apache httpd.conf and its ErrorLog directive.
/var/log/nginx/nginx_error.log for NGINX.
C:\inetpub\logs\LogFiles for IIS.
Luckily this is uncommon still, but journalctl -r -u apache2.service could also hold parts of the log on Linux setups.
它是一个文本文件。搜索与错误时间最接近的条目,并使用错误消息的重要部分(从“PHP error:…”到“in line…”)进行进一步的google搜索。
[Mon 22:10] [:error] [pid 12345] [client 127.0.0.1] FastCGI: server "/fcgi/p73" stderr: PHP message:PHP error: Unfiltered inputvariable $_JSON['pokestop_lng'] in filyfile.php on line 845
对于FPM设置,你经常会看到致命的PHP错误。而旧的mod_php(共享主机)配置经常混合警告和通知(通常也值得检查)。
如果没有配置为使用系统或Apache日志机制,您可能还需要查看PHP的error.log。一般来说,保留默认值并启用error_display + error_reporting来显示具体的错误会更简单。HTTP 500全捕获页面不过是PHP死机白屏幕的一个变种。
参见:
500内部服务器错误的php文件,而不是html
我怎么能让PHP显示错误,而不是给我500内部服务器错误
如何在IIS7上显示和记录PHP错误?
如何修复WordPress内部服务器的500个错误
致命错误:允许的内存大小XXX字节已耗尽(已尝试分配XXX字节)
没有足够的内存来运行脚本。PHP已达到内存限制并停止执行。这个错误是致命的,脚本停止。内存限制的值可以在php.ini文件中配置,也可以使用ini_set('memory_limit', '128 M');在脚本中(将覆盖php.ini中定义的值)。内存限制的目的是防止一个PHP脚本占用所有可用内存,导致整个web服务器瘫痪。
The first thing to do is to minimise the amount of memory your script needs. For instance, if you're reading a large file into a variable or are fetching many records from a database and are storing them all in an array, that may use a lot of memory. Change your code to instead read the file line by line or fetch database records one at a time without storing them all in memory. This does require a bit of a conceptual awareness of what's going on behind the scenes and when data is stored in memory vs. elsewhere.
如果在脚本没有执行内存密集型工作时发生此错误,则需要检查代码以查看是否存在内存泄漏。memory_get_usage函数是您的朋友。
相关问题:
所有“Fatal error: Allowed memory size of XXX bytes exhausted”问题
mysql_connect(): user 'name'@'host'拒绝访问
当您连接到无效或缺少凭据(用户名/密码)的MySQL/MariaDB服务器时,会出现此警告。所以这通常不是代码问题,而是服务器配置问题。
See the manual page on mysql_connect("localhost", "user", "pw") for examples.
Check that you actually used a $username and $password.
It's uncommon that you gain access using no password - which is what happened when the Warning: said (using password: NO).
Only the local test server usually allows to connect with username root, no password, and the test database name.
You can test if they're really correct using the command line client:
mysql --user="username" --password="password" testdb
Username and password are case-sensitive and whitespace is not ignored. If your password contains meta characters like $, escape them, or put the password in single quotes.
Most shared hosting providers predeclare mysql accounts in relation to the unix user account (sometimes just prefixes or extra numeric suffixes). See the docs for a pattern or documentation, and CPanel or whatever interface for setting a password.
See the MySQL manual on Adding user accounts using the command line. When connected as admin user you can issue a query like:
CREATE USER 'username'@'localhost' IDENTIFIED BY 'newpassword';
Or use Adminer or WorkBench or any other graphical tool to create, check or correct account details.
If you can't fix your credentials, then asking the internet to "please help" will have no effect. Only you and your hosting provider have permissions and sufficient access to diagnose and fix things.
Verify that you could reach the database server, using the host name given by your provider:
ping dbserver.hoster.example.net
Check this from a SSH console directly on your webserver. Testing from your local development client to your shared hosting server is rarely meaningful.
Often you just want the server name to be "localhost", which normally utilizes a local named socket when available. Othertimes you can try "127.0.0.1" as fallback.
Should your MySQL/MariaDB server listen on a different port, then use "servername:3306".
If that fails, then there's a perhaps a firewall issue. (Off-topic, not a programming question. No remote guess-helping possible.)
When using constants like e.g. DB_USER or DB_PASSWORD, check that they're actually defined.
If you get a "Warning: Access defined for 'DB_USER'@'host'" and a "Notice: use of undefined constant 'DB_PASS'", then that's your problem.
Verify that your e.g. xy/db-config.php was actually included and whatelse.
Check for correctly set GRANT permissions.
It's not sufficient to have a username+password pair.
Each MySQL/MariaDB account can have an attached set of permissions.
Those can restrict which databases you are allowed to connect to, from which client/server the connection may originate from, and which queries are permitted.
The "Access denied" warning thus may as well show up for mysql_query calls, if you don't have permissions to SELECT from a specific table, or INSERT/UPDATE, and more commonly DELETE anything.
You can adapt account permissions when connected per command line client using the admin account with a query like:
GRANT ALL ON yourdb.* TO 'username'@'localhost';
If the warning shows up first with Warning: mysql_query(): Access denied for user ''@'localhost' then you may have a php.ini-preconfigured account/password pair.
Check that mysql.default_user= and mysql.default_password= have meaningful values.
Oftentimes this is a provider-configuration. So contact their support for mismatches.
Find the documentation of your shared hosting provider:
e.g. HostGator, GoDaddy, 1and1, DigitalOcean, BlueHost, DreamHost, MediaTemple, ixWebhosting, lunarhosting, or just google yours´.
Else consult your webhosting provider through their support channels.
Note that you may also have depleted the available connection pool. You'll get access denied warnings for too many concurrent connections. (You have to investigate the setup. That's an off-topic server configuration issue, not a programming question.)
Your libmysql client version may not be compatible with the database server. Normally MySQL and MariaDB servers can be reached with PHPs compiled in driver. If you have a custom setup, or an outdated PHP version, and a much newer database server, or significantly outdated one - then the version mismatch may prevent connections. (No, you have to investigate yourself. Nobody can guess your setup).
更多的引用:
mysql服务器错误:mysql用户无法访问root用户
mysql_connect():拒绝访问
mysql_select_db()拒绝访问用户" @'localhost'(使用密码:NO)
PHPMyAdmin拒绝用户“root”@“localhost”的访问
顺便说一句,你可能不想再使用mysql_*函数了。新来者经常迁移到mysqli,然而这也一样乏味。相反,阅读PDO和准备好的语句。
$db =新PDO("mysql:主机=localhost;dbname=testdb", "用户名","密码");
警告:[function]: failed to open stream: [reason]
当你通过include, require或fopen调用一个文件时,PHP无法找到该文件或没有足够的权限来加载该文件。
这种情况的发生有多种原因:
文件路径错误
文件路径是相对的
包含路径是错误的
权限限制太大
SELinux已生效
还有更多……
一个常见的错误是不使用绝对路径。这可以通过使用完整路径或神奇常数如__DIR__或dirname(__FILE__)轻松解决:
include __DIR__ . '/inc/globals.inc.php';
or:
require dirname(__FILE__) . '/inc/globals.inc.php';
确保使用正确的路径是排除这些问题的一个步骤,这也可能与不存在的文件、文件系统的权限阻止访问或PHP本身的打开basedir限制有关。
快速解决此问题的最佳方法是遵循下面的故障排除清单。
相关问题:
故障排除清单:无法打开流
相关的错误:
警告:open_basedir限制生效
HTTP错误500 -内部服务器错误
HTTP状态代码500和典型的Apache或浏览器警告是一个非常广泛的消息。这不是实际的错误。要弄清楚是web服务器配置错误(.htaccess)还是PHP致命错误,你必须查看error.log。
你通常可以在下面找到webservers日志:
/var/log/apache2 on Linux servers, often used for local and virtual hosts.
/var/www/_user12345_/logs or similar on shared hosting plans.
Usually there's a logs/ directory alongside each htdocs/ folder.
C:\xampp\apache\logs\error.log for WAMP/XAMPP distributions of Apache+PHP.
Alternatively just use a file search feature to locate anything called "error.log".
Or look into your Apache httpd.conf and its ErrorLog directive.
/var/log/nginx/nginx_error.log for NGINX.
C:\inetpub\logs\LogFiles for IIS.
Luckily this is uncommon still, but journalctl -r -u apache2.service could also hold parts of the log on Linux setups.
它是一个文本文件。搜索与错误时间最接近的条目,并使用错误消息的重要部分(从“PHP error:…”到“in line…”)进行进一步的google搜索。
[Mon 22:10] [:error] [pid 12345] [client 127.0.0.1] FastCGI: server "/fcgi/p73" stderr: PHP message:PHP error: Unfiltered inputvariable $_JSON['pokestop_lng'] in filyfile.php on line 845
对于FPM设置,你经常会看到致命的PHP错误。而旧的mod_php(共享主机)配置经常混合警告和通知(通常也值得检查)。
如果没有配置为使用系统或Apache日志机制,您可能还需要查看PHP的error.log。一般来说,保留默认值并启用error_display + error_reporting来显示具体的错误会更简单。HTTP 500全捕获页面不过是PHP死机白屏幕的一个变种。
参见:
500内部服务器错误的php文件,而不是html
我怎么能让PHP显示错误,而不是给我500内部服务器错误
如何在IIS7上显示和记录PHP错误?
如何修复WordPress内部服务器的500个错误
注意:试图获取非对象错误的属性
在没有对象时试图访问对象的属性时发生。
非对象通知的一个典型例子是
$users = json_decode('[{"name": "hakre"}]');
echo $users->name; # Notice: Trying to get property of non-object
在本例中,$users是一个数组(因此不是一个对象),它没有任何属性。
这类似于访问数组中不存在的索引或键(参见注意:未定义索引)。
这个例子简化了很多。大多数情况下,这样的通知表示一个未检查的返回值,例如,如果一个对象不存在,或者只是一个意外的非对象值(例如,在Xpath结果中,具有意外格式的JSON结构,具有意外格式的XML等),库将返回NULL,但代码不会检查这样的条件。
由于这些非对象通常会被进一步处理,因此在对非对象调用对象方法时经常会发生致命错误(参见:致命错误:调用成员函数…在非对象上)停止脚本。
通过检查错误条件和/或变量是否符合期望,可以很容易地防止这种情况。下面是一个带有DOMXPath示例的通知:
$result = $xpath->query("//*[@id='detail-sections']/div[1]");
$divText = $result->item(0)->nodeValue; # Notice: Trying to get property of non-object
问题是访问第一项的nodeValue属性(字段),而没有检查它是否存在于$result集合中。相反,通过将变量分配给代码所操作的对象,可以使代码更加显式:
$result = $xpath->query("//*[@id='detail-sections']/div[1]");
$div = $result->item(0);
$divText = "-/-";
if (is_object($div)) {
$divText = $div->nodeValue;
}
echo $divText;
相关的错误:
注意:未定义索引
致命错误:调用成员函数…在一个非物体上