Thank you.
]]>This was in the error log.
“PHP Fatal error: Can’t use method return value in write context in /var/www/html/news/wp-content/plugins/somewhere-search-box/somewhere-search-box.php on line 233”
Same thing has happened when I had updated “Hide Update Reminder” to 1.3.0 from 1.2.1. The culprit was that the author modernized its code. Right now, the author has fixed it and no error happens.
Anyways, the server info that made this error are as follows:
Server Info:
WordPress
Version 4.8
Language ja
Charset UTF-8
Memory Limit 40M (Max 256M)
PHP
Version 5.3.3
SAPI apache2handler
User apache
Process apache
Safe Mode Off
Memory Limit 256M
Memory In Use 57.00 MB
Max Execution Time 30
Shell Exec Is Supported
Shell Exec Zip Is Supported
Suhosin Extension Disabled
MySQL
Version 5.0.45
Comments Source distribution
Charset utf8
Wait Timeout 28800
Max Allowed Packets 1048576
msyqldump Path /usr/bin/mysqldump
I hope that you’ll be able to fix this for people like us with old php and mysql servers which we cannot update on our own.
]]>This was in the error log.
“PHP Parse error: syntax error, unexpected T_OBJECT_OPERATOR in /var/www/html/news/wp-content/plugins/wp-social-bookmarking-light/wp-social-bookmarking-light.php on line 44”
Same thing has happened when I had updated “Hide Update Reminder” to 1.3.0 from 1.2.1. The culprit was that the author modernized its code. Right now, the author has fixed it and no error happens.
Anyways, the server info that made this error are as follows:
Server Info:
WordPress
Version 4.8
Language ja
Charset UTF-8
Memory Limit 40M (Max 256M)
PHP
Version 5.3.3
SAPI apache2handler
User apache
Process apache
Safe Mode Off
Memory Limit 256M
Memory In Use 57.00 MB
Max Execution Time 30
Shell Exec Is Supported
Shell Exec Zip Is Supported
Suhosin Extension Disabled
MySQL
Version 5.0.45
Comments Source distribution
Charset utf8
Wait Timeout 28800
Max Allowed Packets 1048576
msyqldump Path /usr/bin/mysqldump
I hope that you’ll be able to fix this for people like us with old php and mysql servers which we cannot update on our own.
]]>My host server is RH CentOS 6.x.
CentOS 6.x is running PHP-5.3.3, which is maintained security of PHP by yum update in automatically.
CentOS 6.x will updating PHP for the security it self.
So, if WooCommerce recommendation is only for the security, PHP-5.3.3 will be used with WooCommerce store.
If security is ok, can I use PHP-5.3.3 with the WooComerce-2.4.7 without functioning problem ?
]]>I got the following problem (only on my online server):
My 404.php template is not loaded by WP during an unknown page/post request.
Online server is running:
– PHP Version 5.3.3-7+squeeze3
– Apache/2.2.16 (Debian)
After some debugging I tackled down the occurrence of the problem:
During the request WP sets the header to 404 in the following file ‘wp-includes/functions.php’ with function ‘status_header( 404 )’.
The ‘status_header’ functions calls the PHP ‘header’ function which results in a “404 Not Found” page where it should load the ‘404.php’ template.
I guess this is a server related problem. Anybody some ideas?
thanks in advance!
]]>