gophp5 but why does it have to be 5.2
Posted: Fri Jan 18, 2008 7:40 pm
http://blog.cmsmadesimple.org/2007/07/08/gophp5/
In regards to the above about the future of cmsms using php 5.2 - is this still something we need to consider still since cmsms 2 is likely not coming out until later... Will cmsms 1.2.3 etc still be supported in terms of security fixes?
The problem with upgrading is this is from the host:
"The upgrade of PHP is not an easy one due to the many parts of the LAMP stack it integrates with. During an unsupported upgrade (compiled from source, not a package from the upstream provider) there is a significant risk of sites being down and displaying raw PHP."
How would you even go about doing this if you have many sites on a dedicated server (with different Open Source apps). You can't shut all the site down for the upgrade and hope all the sites will work after...
So does cmsms not care as much to the userbase and just hope that follower will change host? Just want to know ahead before getting in too deep in cmsms...
In regards to the above about the future of cmsms using php 5.2 - is this still something we need to consider still since cmsms 2 is likely not coming out until later... Will cmsms 1.2.3 etc still be supported in terms of security fixes?
The problem with upgrading is this is from the host:
"The upgrade of PHP is not an easy one due to the many parts of the LAMP stack it integrates with. During an unsupported upgrade (compiled from source, not a package from the upstream provider) there is a significant risk of sites being down and displaying raw PHP."
How would you even go about doing this if you have many sites on a dedicated server (with different Open Source apps). You can't shut all the site down for the upgrade and hope all the sites will work after...
So does cmsms not care as much to the userbase and just hope that follower will change host? Just want to know ahead before getting in too deep in cmsms...
