check the suphp how to in the guides section that is workable, I have it setup so php4 is a module and works completely normal and php5 as cgi. It is possible with htaccess files as well to make .php use php5.
I think with the current GoPHP5 campaign -- DirectAdmin should also assist and commit to dropping php4.
The majority known and supported apps are committed to going to php5. It's the old/unsupported apps that are likely to get left with php4. That in itself is enough of a security risk that the apps also die a cruel death.
Sure run php4 for the next 6 months.. .but it's needing to die so developers of PHP4 can bury the thing.
We've got a new build script here, which installs apache 2.2 and php5 by default. We're working on adding install time options in the setup.sh to give admins the option of installing it. Right now you already can by simply typing:
Code:
touch /root/.custombuild
prior to running the setup.sh, and the installer will find it and take care of the rest.
While php5 does have all the capabilities of php4, in the beginning there were incompatibilities and caveats which caused php5 not able to just drop in place of php4 and keep everything running.
This may not be so much the case anymore. Though I still hear all the time about hosts going from php4 to 5 and many users scripts breaking in the process. Usually only needing small tweaks if any... But none the less not 100% backwards compatible IMHO
It depends on circumstances but if one has customers needing php4 which they cant afford to lose then that is a reason to keep php4. I dont see any harm in a configuration that has both php5 and php4.