Title speaks for itself really. PHP 5.4 is the latest stable version of PHP and has been released for more than 3 months.
Title speaks for itself really. PHP 5.4 is the latest stable version of PHP and has been released for more than 3 months.
Theres 2 stable versions for each branch, 5.3.14 and 5.4.4. 90% of hosting services use php 5.2/5.3 and thats the reason each release is tested with those versions. But yes, they should also make php 5.4 compatible in next updates.
http://whmcsmod.com
Custom WHMCS modules
Livedrive Backup | Cloudberry Backup | Sermepa | Smartermail | Teamspeak 3 | Leaseweb | Hetzner |
Providing you have the PHP 5.4 Ioncube loaders it should already work. Are you experiencing a particular problem?
Matt
Frank Laszlo
Developer - Franksworld Solutions, LLC
Modules: ServerUptime|UnBlockMe|Admin IP Whitelist|Regional Promotions|Affiliate Coupons|GoogleApps|Signed Invoices|Samurai Payment Gateway|Twilio Call-Redirect
OK, thanks for the affirmation there. After some tinkering with memcached and a switch to 5.4.4 (instead of 5.4.3) I got it working, so we're happy once more.
Do you mind sharing with the rest of us what sort of tinkering you did to get it to work with 5.4.4? I too can confirm that search and client login are broken.
Last edited by Slice; 07-21-12 at 07:14 PM.
Never went back and retried 5.4.3, but 5.4.4 wasn't that big a problem really. Main thing there was to be sure to empty the templates_c directory and clear out any other caching mechanisms you may have.
We had issues with PayPal callbacks / IPN notifications not working correctly. Once we downgraded to 5.3 everything is working again.
Thanks, guys. I had to go between 5.2, 5.3 and 5.4 with a lot of tweaking of the php.ini and recompliling before I was able to resolve conflicts and problems. The end result is I ended up with PHP 5.4.5 with no errors with php -v and all functionality restored with WHMCS. I am going to do some further investigation tomorrow in order to understand what where the specific, and definitely multiple, problems were.
So far I've narrowed down the problem to the example production php.ini and I'm trying to track down the exact line causing the bug. Anybody want to take an educated guess?
It's somewhere below the Module Settings section, outside of the [PHP] context.