October 12, 2009
Starting at the beginning of 2010, all of Solspace’s codebase will begin the transition from supporting PHP 4 to requiring PHP 5. We will begin requiring MySQL 4.1+ as well. This change will not happen overnight, but all new code will be written with this goal in mind.
Over the previous six months, Solspace has released new versions of its popular Add-Ons with many of these new versions requiring a minimum of PHP 4.3.2 and MySQL 4.1. This is because there are new features and abilities available in the more recent versions of PHP and MySQL that Solspace wishes to take advantage of.
The transition to PHP 5 has a similar justification, but it is also taking into account the fact that official support of PHP 4 has been over for quite a while now and nearly all of our long term clients and partners have finally made the switch to PHP 5 on their servers. We feel we can finally start updating our code without negatively impacting our clients and users.
There are still a few holdouts using PHP 4 though, which is why we are announcing this transition ahead of time. You will have a minimum of two and a half months to successfully switch your setups to use PHP 5. If you have any questions or concerns, please feel free to post them in our support forums and we will address them as best we can.
Further, at the same time, Solspace will be deprecating support for Internet Explorer 6 in our Add-Ons. This does not mean we will completely ignore IE 6, but if getting an interface to work in IE6 causes too much trouble there is a fair chance we will make that Add-On IE6 incompatible. Naturally, we still suggest that all IE users to switch to Firefox or Safari at your earliest convenience
Tags: php, mysql, ie6, development, addons
Comments
That’s great news!
Although PHP4 didn’t add too much of a support overhead for our addons, IE6 did. As a result we dropped IE6 support a long time ago.
Posted by Newism on October 12, 2009 at 6:03 pm
Probably should mention that we have also dropped PHP4 support for all of our new addons.
Posted by Newism on October 13, 2009 at 4:10 am
I would have liked to do it (far) sooner, but we had clients that simply would not budge on either issue. Comes a time though when you simply have to bite the bullet and issue a proclamation so that you can move on.
Posted by Paul Burdick on October 13, 2009 at 7:57 am
Didn’t Mitchell just turn 37? When will he be deprecated to make way for his newer and improved clone?
Posted by John Fuller on October 13, 2009 at 10:50 pm
Ahahahahaha
Posted by Kelsey Martens on October 14, 2009 at 10:40 am
The scariest of these, to me, is MySQL 3. Not that there are many major hurdles to supporting MySQL 3, save a few niceties, it’s just the thought of someone paying a host out there that’s still running MySQL 3 (and they <em>do</em> exist). How out of date is every other component? ::shudder::
Posted by Derek Jones on October 15, 2009 at 3:23 pm