Cyclone Hosting practical guide: Changing PHP can improve compatibility and security, but applications and extensions must be tested together.
Why PHP Version Matters
PHP powers many websites, including WordPress and custom applications. Newer versions often improve performance and security, but older software may not be compatible.
Back Up Before Changing
Create a current backup of files and databases. A PHP change can expose errors that were hidden on the previous version.
Check Application Requirements
Review the requirements for your content management system, plugins, themes, and custom code. Pay special attention to older extensions and encrypted software.
Use The cPanel PHP Selector
Depending on the server, the tool may be called MultiPHP Manager, Select PHP Version, or something similar. Choose the domain and select the supported version.
Review Extensions
Some applications require extensions such as mysqli, mbstring, intl, zip, curl, gd, or imagick. Confirm required extensions are enabled after changing versions.
Test The Entire Website
- Open public pages.
- Log in to the administrator area.
- Submit forms.
- Test checkout or account features.
- Review the error log.
Do Not Ignore Warnings
Deprecated warnings may not break the site today, but they show that code needs attention. Fatal errors usually require updating or replacing incompatible software.
Roll Back If Necessary
If the site stops working, return to the previous PHP version while you investigate. Do not leave the website broken while experimenting on production.
Cyclone Hosting Practical Checklist
- Check the application requirements before switching.
- Record the current version so you can roll back.
- Test forms, logins, payments, and scheduled tasks afterward.
- Review error logs for deprecated code and missing extensions.
When To Contact Support
Contact Cyclone Hosting support when the issue involves the hosting account, server access, DNS hosted with us, email-server settings, SSL issuance, or an error you cannot isolate. Include the domain, the exact error, the page or mailbox affected, when it began, and the troubleshooting already attempted. Never send a password in a normal support message.
What To Record For Future Reference
Keep a short change log containing the date, the setting changed, the reason for the change, and the backup or rollback point. This makes future troubleshooting faster and helps separate a hosting problem from an application change.