致命错误:未定义类常量

此错误意味着您试图使用不存在的类常量。与其他“未定义”的通知和警告不同，这是一个致命错误，将立即停止脚本。

首先要检查的是印刷错误。确认在类中定义了常量，并且使用适当的名称空间调用它。还要确认已包含用于解析常量的所有适当文件。

致命错误:允许的内存大小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”问题

解析错误:语法错误，意外的T_PAAMAYIM_NEKUDOTAYIM

范围解析操作符也被称为“Paamayim Nekudotayim”，源自希伯来语פייםנקדיים”。意思是“双冒号”。

如果您无意中在代码中放入::，则通常会发生此错误。

相关问题:

参考:PHP语法错误;以及如何解决这些问题? PHP中两个冒号是什么意思? 在PHP中::(双冒号)和->(箭头)之间的区别是什么? 意外T_PAAMAYIM_NEKUDOTAYIM，期望T_NS_Separator

文档:

范围解析运算符(::)

解析错误:语法错误，意外的T_VARIABLE

可能的场景

我似乎找不到我的代码出了什么问题。以下是我的全部错误:

解析错误:语法错误，意外的T_VARIABLE在x行

我正在尝试的

$sql = 'SELECT * FROM dealer WHERE id="'$id.'"';

回答

解析错误:程序的语法问题，例如在语句的末尾遗漏了分号，或者像上面的情况一样，遗漏了。操作符。解释器在遇到解析错误时停止运行程序。

简单地说，这是一个语法错误，这意味着您的代码中有一些东西阻止了它被正确解析，从而无法运行。

您应该做的是仔细检查错误所在的行周围是否有任何简单的错误。

该错误消息意味着，在文件的第x行，PHP解释器期望看到一个开括号，但相反，它遇到了名为T_VARIABLE的东西。T_VARIABLE这个东西叫做令牌。它是PHP解释器表达程序不同基本部分的方式。当解释器读入程序时，它将您所编写的内容转换为令牌列表。无论你在程序中放入一个变量，解释器的列表中都会有一个aT_VARIABLE令牌。

不错的阅读:解析器令牌列表

因此，请确保在php.ini中至少启用了E_PARSE。产品脚本中不应该存在解析错误。

我总是建议在编码时添加以下语句:

error_reporting(E_ALL);

PHP错误报告

另外，使用IDE是个好主意，它可以让你在输入时知道解析错误。你可以使用:

NetBeans(一个漂亮的免费软件)(在我看来是最好的) PhpStorm(戈登叔叔喜欢这个:P，付费计划，包含专有和免费软件) Eclipse(美女与野兽，免费软件)

相关问题:

参考:PHP语法错误;以及如何解决这些问题?

致命错误:[TraitA]和[TraitB]在[ClassC]组合中定义相同的属性([$x])

当类试图使用多个trait时发生，其中两个或多个trait定义了同名的属性，且属性具有不同的初始值。

例子:

<?php
trait TraitA
{
    public $x = 'a';
}
trait TraitB
{
    public $x = 'b';
}
class ClassC
{
    use TraitA, TraitB;
}

问题:虽然可以解决相互竞争的方法之间的冲突，但目前没有语法可以解决两个相互竞争的属性之间的冲突。此时唯一的解决方案是重构;也就是说，避免属性名之间产生致命错误的冲突。

相关问题:

PHP特征:如何解决属性名称冲突? 特征-属性与父类冲突

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"， "用户名"，"密码");