Drop PHP 4.x and MySQL 4.x support

Do you think it's time to drop PHP 4.x and MySQL 4.x support?

  • Total voters
    25
Yea i'm agreed with this one. I've been running PHP 5.x and MySQL 5.x for 12 months now, I've not looked back and have had no complaints from my users.
 
I voted no only because DirectAdmin should give users some time period warning; there are some admins out there who will want to update on their own time schedule, not on one imposed by DirectAdmin. (I'm one of those; we've started moving users on their request but we want to wait a few months before forcing users to make the move, in case some of them might have problems.)

Jeff
 
jlasman, I'm talking about CustomBuild 1.2 as default and mark CustomBuild 1.1 EOL. You'll be able to use CustomBuild 1.1 (as you're able to use frontpage extensions now), but you'll get no support for it. I'm not talking about removal of PHP or MySQL packages from DA servers :)
 
i'm with you
but there are many people that dont agree with us
beacuse they like this ver
ok beacuse they dont have time to update
it's a many reason
 
thanks for the clarification, smtalk.

I've got a client that wants to update from CustomApache to custombuild 1.1. Should I recommend 1.2 instead?

Thanks.

Jeff
 
If he wants PHP5 and MySQL5 then you should go with 1.2 :) It's stable enough.
 
voted no, although for the people who always follow latest releases of everything it seems logical, the simple fact there is many sites out there that still require php4.

I got no issue if php5 and mysql5 are defaults but support should remain for older versions as long as demand is still there.
 
Thank you for your opinion, but I didn't say PHP4 will be removed from DirectAdmin servers :) PHP4 is EOL, so I think CustomBuild 1.1 should be EOL too.
 
smtalk said:
Thank you for your opinion, but I didn't say PHP4 will be removed from DirectAdmin servers :) PHP4 is EOL, so I think CustomBuild 1.1 should be EOL too.
Click to expand...

well removing it from the scripts is effectively the same thing. Whats so bad about keeping it there as an option? the code is already there. It just seems too soon after php4 went offically EOL.
 
Voted no for upgrade purposes...... although, for clean installations I'd say yes.

Also, if a PHP4/Ap1.3/MySQL4.x server hosts, say, ~400 sites, you upgrade everything, only to find everything broken after..... There would be some very angry customers........

Yes, I'm a pessimist...... I want to upgrade to PHP5, but do I have the guts to, nooooo..... :(
 
yes.
vBulletin 4, Invision Power Board 3, PhpMyAdmin 3....will require PHP 5.x & MySQL 5.X, so i think that's the right time to drop PHP 4 & MySQL 4
:)
 
Peter Laws said:
Voted no for upgrade purposes...... although, for clean installations I'd say yes.

Also, if a PHP4/Ap1.3/MySQL4.x server hosts, say, ~400 sites, you upgrade everything, only to find everything broken after..... There would be some very angry customers........
Click to expand...

But why DA needs to support outdated software with its stable (not outdated) scripts (as CustomApache or CustomBuild)? And how it can be supported if software is no longer developed (and you can not get any support from developers)?

Peter Laws said:
Yes, I'm a pessimist...... I want to upgrade to PHP5, but do I have the guts to, nooooo..... :(
Click to expand...
I can help you to upgrade PHP 4 to PHP 5 if you want :)
 
I definately do not agree since the websites I have programmed need to be rewritten for PHP5, and that's gonna take a lot of time when you have a day job too... So I would say give me a 2-5 year notice before getting rid of the PHP4 support.. LOL
 
There are very few if any changes that have to made to any php scripts in order to use php5. I exclusively use php5 for almost a year have have very few problems from the thousands of php web sites we host.

dreamline I know you may be an exception. I am just saying generally there are very few problems with upgrading. You have already the 2-5 year notice though. Everyone knew with the inception of php5 that php4 would be going away. Everyone has already had about 4 years notice.
 
I've voted 'YES', why?

- First PHP4 is EOL
- Most scripts in PHP4 are not save, like don't using $_GET $_POST
- PHP.NET don't make bug-fixes anymore for PHP4 so each next day it will be more risky to use it.
- Its time for the scripters to learn PHP5 and/or make your PHP-scripts compatible for any PHP version as possible.
 
You must log in or register to reply here.
Back
Top