Frequently asked questions

Back
Keyword:  

Are there known problems with the PHP 5.3 upgrade in 2012?
Yes, some of our customers experience problems after the upgrade.

Problems usually occur when the webhotel is configured for PHP 5.2, and the webhotel's administrator hasn't upgraded yet.

Here is an overview of known problems and solutions, written for those with the technical responsibility for the webpages. This is not a complete list of all possible problems, only the most frequently encountered. If neither of these hints solve your problem, try installing your software from scratch, and enabling components/extensions/plugins/themes one by one to see where the problems occur.

Please note that php.ini is often loaded by the file .htaccess, which may reside in the webhotel's main folder, the www folder, or in a subfolder. Many FTP and shell software hide files with a leading dot in the filename. Some customers also load php.ini from other websites.



MySQL

SymptomCauseSolution
Fatal error: Call to undefined function mysql_connect() Specific php.ini created for PHP 5.2 overrides the central php.ini. MySQL functionality is integrated in the server configuration, but is disabled by your specific php.ini. Remove php.ini.
Database Error: Unable to connect to the database:The MySQL adapter "mysql" is not available. Error message from Joomla. Specific php.ini created for PHP 5.2 overrides the central php.ini. MySQL functionality is integrated in the server configuration, but is disabled by your specific php.ini. Remove php.ini.
Your PHP installation appears to be missing the MySQL extension which is required by WordPress. Error message from Wordpress. Specific php.ini created for PHP 5.2 overrides the central php.ini. MySQL functionality is integrated in the server configuration, but is disabled by your specific php.ini. Remove php.ini.

Joomla

SymptomCauseSolution
The webpages don't work at all, cannot administer Joomla
  • Old Joomla versions do not support PHP 5.3
  • or there are similar problems as those mentioned below for Wordpress.
  • Install the most recent Joomla
  • or see if the problem is similar to any of the Wordpress problems. Note: Wordpress' standard .htaccess does not fit Joomla!
Database Error: Unable to connect to the database:The MySQL adapter "mysql" is not available. Error message from Joomla. Specific php.ini created for PHP 5.2 overrides the central php.ini. MySQL functionality is integrated in the server configuration, but is disabled by your specific php.ini. Remove php.ini.
Joomla 3.0 does not install, and complains about Magic Quotes GPC/magic_quotes_gpc magic_quotes_gpc is deprecated in PHP 5.3, yet enabled by default. Joomla 3.0 does not thrive with that. magic_quotes_gpc is removed from PHP 5.5. Disable magic_quotes_gpc by creating your own .user.ini

Wordpress

SymptomCauseSolution
Pages with URLs similar to http://www.example.com/?page_id=53 etc. are not displayed/do not work
  • Standard .htaccess for Wordpress is missing in the Wordpress folder
  • or .htaccess exists, but the standard Wordpress contents are missing.
Pages with URLs similar to http://www.example.com/?page_id=53 etc. are not displayed/do not work, and the above solutions fix nothing
  • This may be related to upgrading from an older version of Wordpress and/or old themes/plugines
  • or permalinks.
  • If you do not use permalinks, try to enable one type and save your configuration, and experiment a bit with different types of permalinks.
  • If none of these tips solve the problems, we recommend that you use the Wordpress forum for help.
404 Not Found
  • Standard .htaccess for Wordpress is missing in the Wordpress folder
  • or .htaccess exists, but is missing the standard Wordpress contents.
403 Forbidden
  • Standard .htaccess for Wordpress is missing int he Wordpress folder
  • or .htaccess exists, but is missing the standard Wordpress contents
  • or .htaccess finnes, but has other errors. See also the below explanation for 500 Internal Server Error.
See the below solution for 500 Internal Server Error.
500 Internal Server Error You have a specific .htaccess with code similar to this:
AddType application/x-http-php .php .html .htm.
PHP filenames must end with .php, AddType cannot reliably be redefined. This was not and is not supported configuration.
Your PHP installation appears to be missing the MySQL extension which is required by WordPress. Error message from Wordpress. Specific php.ini created for PHP 5.2 overrides the central php.ini. MySQL functionality is integrated in the server configuration, but is disabled by your specific php.ini. Remove php.ini.

Wordpress' standard .htaccess

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

IonCube

SymptomCauseSolution
  • The webpages do not work
  • IonCube Loader is missing
You have a specific php.ini for PHP 5.2, and IonCube is installed for PHP 5.2 and/or 32-bit Linux
  • Note: we do not provide support for such configurations.
  • Remove php.ini.
  • Install the most recent IonCube for PHP 5.3 and Linux x86-64.
  • Install new specific php.ini for PHP 5.3.

Zend Optimizer

SymptomCauseSolution
  • The webpages do not work
  • Zend Optimizer is missing
  • Zend Guard Loader is missing
You have a specific php.ini for PHP 5.2, and Zend Optimizer does not support PHP 5.3.
  • Note: we do not provide support for such configurations.
  • Remove php.ini.
  • Install new specific php.ini for PHP 5.3 and enable Zend Guard Loader.
  • The webpages do not work
  • Error message about Zend encoding for version 3, but only version 4 is supported
Your PHP software is encrypted with an outdated version of Zend Guard, and must be reencrypted with a current version.
  • Note: we do not provide support for such configurations.
  • Upgrade your software to a version encrypted with the current Zend Guard, compatible with the version mentioned in the error message. Your software vendor and Zend have more information.

Specific php.ini

SymptomCauseSolution
php.ini is loaded in subfolders (but not the webhotel's main folder) even though it isn't configured in .htaccess A bug in suphp loads php.ini too eagerly.
  • Remove php.ini.
  • If you require a specific php.ini, add it explicitly to .htaccess, if you don't, remove php.ini.
php.ini is not automatically reloaded after a change Filesystem cache lasting (1) minute Wait (1) minute and see if that solves the problem.

Cron jobs

SymptomCauseSolution
The cron job does not run Path to PHP, Perl etc. was entered with /usr/local/bin. Use /usr/bin instead.

See also:

© 2024 Domeneshop AS · About us · Terms · Privacy policy