There is a bug in php 5.3 with the iconv module. Apple applied a patch for their version of php. However, MAMP didn't include this patch and is thus unusable with Zend Framework (for example).
I tried to include Apple's version of php 5.3 into the MAMP's httpd.conf, but ran into problems with symbols which could not be found. Does anyone know of a proper way to use MAMP with php 5.3 /w iconv? Is recompiling or linking apple's version an option?
Just rename the php directories in /Applications/MAMP/bin/php
Duplicate php 5.3 directory and rename it to the same ver number of 5.2, and it works. :d
I'm not sure this leave a whole lot of value in the MAMP, but you probably are best served compiling your own php and apache.
http://fabien.potencier.org/article/37/php-5-3-0-on-mac-os-10-6-snow-leopard
There is a discussion of this issue here:
iconv_strlen function causing execution timeout, running on MAMP
The basic solution is either to downgrade your MAMP to version 1.9.4 which is the last stable version as far as “iconv” is concerned. Or you can use any version of MAMP from 1.9.5 onwards but switch the PHP version from the MAMP preferences from 5.3 to 5.2.
Related
I need to install a plugin on my website which requires PHP >= 5.5. Right now i'm running PHP 5.3.3 on CentOS 6.6.
Is it safe tou upgrade PHP or there is a a tangible risk that some
applications won't work after upgrade?
Is there a way to "rollback" the upgrade? So that i upgrade, i check that everything works and, if not, i downgrade.
Thanks!
Yes, there is a chance that some applications won't work. I upgraded from 5.3 to 5.4 on a system and found that a bug appeared in production code. It wasn't anything that couldn't be fixed. Of course, there have been other times where an upgrade worked flawlessly.
If you install 5.5 on the system without disturbing the 5.3 installation then it should be possible to rollback to 5.3 if needed. Just save the server configuration for 5.3 before pointing it to 5.5.
My site had worked great untill I updated its php version to 5.4.4 (I also tryed 5.3), I can't continue using php v5.2 because I have added some function that are not supported in 5.2 version.
I work on a windows server.
Profile your PHP with xdebug.
You can see PROFILING PHP WITH XDEBUG AND WEBGRIND, the main parser of xdebug files (kcachegrind) is native for Linux.
An alternative is windows port of kcachegrind, but I never tried it.
XHProf is another simple tool for Profiling
It's very simple to use and configure.
I upgraded my system from Windows xp to windows 7. When i was in win xp i used the wamp server with php version 5.0 now i installed the wamp server with the version 5.3. But now it's making problem. The old projects are not running. Even-though they are created in php version 5. How i can solve this problem?
New versions of WAMP use apache 2.2.x and lovest php version supported for that is 5.2. That beeing said you can downgrade your php version of wamp installation by downloading a php addon http://www.wampserver.com/en/addons_php.php from here. Or you can ultimately downgrade WAMP apache installation from 2.2 to 2.0 http://www.wampserver.com/en/addons_apache.php . If your project don't work with 5.2 or 5.3 you need to debug and update your code with the latest changes in php http://php.net/migration53
There are some (but not many) backward-incompatible changes between PHP 5.0 and 5.3. But they're fairly obscure and not generally going to cause major issues. You can find the full details here: http://uk.php.net/manual/en/migration53.incompatible.php
However my guess is that it's more likely that you've installed the new version missing one or more extensions which your code is relying on.
For example, if you are using the pdo_xx() functions, you would need the PDO extension. Most PHP programs will use functionality from several extensions, and not all of them may be included in the default installation, so you need to ensure you have installed with all the ones you need.
The other possibility is that there's an issue with the installation (either PHP itself or the web server, etc) that is preventing PHP from running at all.
But this is all really a guess, because you haven't actually told us anything about what exactly the problem is. You need to look and see in what way it's failing. If you're not getting error messages in the browser, check the server error logs. This is the quickest way to diagnose the problem. It should give you some good clues (if it doesn't help you understand what's happening, paste the relevant log entries here, because they'll definitely make sense to someone)
How on earth does plesk actually work? I have a VPS which is on centos 5.2 and has php 5.1.6. I have updated plesk to version 9.52 and it claimed to do some form of php update but it hasn't as far as i can see. How can i update to php 5.2 (centos 5.4) without breaking plesk Virtuozzo?!
Plesk seems to be some kind of crazy black magic that i just don't understand.
Plesk uses whatever version of PHP is currently installed on the server.
You can update PHP to version 5.2 or higher from the IUS repository, but because Plesk looks in the RPM database specifically for the package "php" and not "php52" it will show that PHP is not installed, and PHP will break. I've gotten around this by compiling a dummy php package, with nothing in it, just called "php" so that Plesk won't disable PHP functionality, but that's not the best way to go.
I am using a joomla templet with XAMPP 1.7.2 which has PHP 5.3.0 in mac os x 10.5.7
i am having lots of trouble like
Deprecated: Function eregi() is deprecated in /Applications/XAMPP/xamppfiles/htdocs/templet01/plugins/system/tbox.php on line 98
Joomla itself is not functioning properly.
Please help.
-Daniel
Is there a release of Joomla that is ready for php 5.3? If so switch to that. Or downgrade XAMPP to a version with php 5.2.X. Or not using XAMPP at all and instead using macports (note if you want php 5.2 youll have to grab the old port file and host a local repo - its not as hard as it sounds - i do it on my machine) or compile the source yourself in /usr/local or /opt.
However it may also be that simply truning off display_errors in your php.ini will fix the issue - or changing the error level.
Joomla 1.5.15 and up is compatible with php 5.3.
However the OpenID authentication module is not yet compatible.