Cmseasy3.9 installation prompt: PHPStrictStandards: Declarationofannouncement: getcols () shouldbecompatiblewiththatoftable: getcols () inD: login: Declaration
Cmseasy3.9 installation prompt: PHP Strict Standards: Declaration of announcement: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2467 PHP Strict Standards: Declaration
Cmseasy3.9 installation prompt:
PHP Strict Standards: Declaration of announcement: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2467
PHP Strict Standards: Declaration of comment: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2492
PHP Strict Standards: Declaration of defind: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2502
PHP Strict Standards: Declaration of event: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2561
PHP Strict Standards: Declaration of friendlink: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2572
PHP Strict Standards: Declaration of guestbook: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2612
PHP Strict Standards: Declaration of linkword: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2626
PHP Strict Standards: Declaration of usergroup: getcols () shocould be compatible with that of table: getcols () in D: \ web \ php \ CmsEasy \ uploads \ lib \ tool \ front_class.php on line 2676
PHP Fatal error: Incompatible file format: The encoded file has format major ID 3, whereas the Loader expects 4 in D: \ web \ php \ CmsEasy \ uploads \ lib \ table \ run. php on line 0
My local machine is iis6 + php5.3.8 + fastCGI +
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
With Zend Guard Loader v3.3, Copyright (c) 1998-2010, by Zend Technologies
Some people say they joined the code at the beginning.
Ini_set ('display _ errors ', '0'); # don't show any errors...
Error_reporting (E_ALL | E_STRICT); #... but do log them
But I added it to index. php.
The latest version
When installing wordpress 3.0.1 in PHP5.3.3, the following error occurs: Strict Standards: PHP Strict Standards: Declaration of Walker:
Error message: Strict Standards: PHP Strict Standards: Declaration of Walker_Page: start_lvl () shocould be compatible with that of Walker: start_lvl () in E: \ Webroot \ wordpress \ wp-uplodes \ classes. php on line 1199 PHP Strict Standards: Declaration of Walker_Page: end_lvl () shocould be compatible with that of Walker: end_lvl () in E: \ Webroot \ wordpress \ wp-uplodes \ classes. php on line 1199 PHP Strict ........
Error cause:
This is because php version 5.3 is later. The inherited class must be defined after the parent class. Otherwise, the following error message is displayed: Strict Standards: PHP Strict Standards: Declaration of... shocould be compatible with that. That is to say, the parent class must be in front, and the inheritance class must be in the back.
Error reference page. Bugs point php point net/bug. php? Id = 46851 (cannot post a URL with a link) The above clearly explains the specific cause of this error.
Work und: In the wordpress3.0.1 file, find the wp-admin \ setup-config.php file. In require_once ('../wp-shortdes/compat. php'); Add the following sentence:
Error_reporting (E_ALL &~ (E_STRICT | E_NOTICE ));
Solve the problem.
The error report setting indicates that all errors are displayed, except for strict error checks or error reports. That is to say, PHP5.3.3 does not perform a strict error check. No error message is displayed. Skip the strict error check.