Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

Installing SilverStripe /

Getting SilverStripe up and running on your computer and on your web server.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba


Go to End

13 Posts   3873 Views


Community Member, 3 Posts

14 October 2009 at 10:34am

I think it will be a very long time before most hosting providers upgrade to PHP 5.3, because serious incompatibles with previously installed software will be a nightmare. I run my own servers and mostly serve my own websites, but even so, upgrading to PHP 5.3 on any of my servers would be sure to take down several active websites and would have difficult-to-anticipate consequences for many other sites. I wrote the code used by most of those sites, but the labor involved to read through tens-of-thousands of lines of code looking for and correcting potential problems is all out of proportion to the advantages PHP 5.3 provides.

The situation is even worse for most public hosting providers, because it is common for them to have hundreds or sometimes even thousands of customers on single servers. A single configuration change in situations like that can, and often does, cause enormous messes and angry customers.

I learned many years go about the importance of naming classes with unique prefixes. It not only greatly reduces the risks of name conflicts, but makes my own names quickly distinguishable even in code I wrote long ago and have almost complete forgotten about. I understand your issues with backward compatibilities, but the sooner the underlying problem is fixed, the fewer old third-party products and users there will be to worry about. It is easy for me to say this as an outsider who doesn't have to deal with the problems, but if I headed your development team, my inclination would be to rename all the classes and deal once with all the resulting backward compatibilities, rather than to change names here and there as necessary to "put out fires."


Forum Moderator, 5523 Posts

14 October 2009 at 10:44am

Vaild Points. Those thoughts might be more useful as part of the core dev mailing list discussion rather then here. But I think a consensus has been reached - that a major renaming effort won't be happening as part of 2.4.


Community Member, 6 Posts

12 November 2009 at 3:30am


So I understand this has been implemented in the core:

I have a simple question: how/where do I get these changes into my wannabe online site (I use FTP to access my hoster). So far, I've downloaded the files from (v2.3.3)



Forum Moderator, 5523 Posts

12 November 2009 at 8:46am

2 ways you can get these changes into your project. Easiest way is if you are on a unix based machine (linux, osx) then you can download that change as a diff file (down the bottom of that page) and run the patch command to apply the diff file using something like this in your command line / terminal.

patch -p0 < ~/path/to/diff/file.diff

Some IDEs like aptana and eclipse also have nice ways to apply diff files.

Or you can download download trunk (and the new 2.4 alpha should have this change as well) and use that.


Community Member, 6 Posts

17 November 2009 at 9:25am

If I stay with version 2.3.3 rather than v2.4 alpha, I need to rename the HTTPResponse class to SSHTTPResponse. But on my XP home edition, the "search word in files" doesn't search inside php files. Is there a workaround?

Go to Top