Installation HELP!!!
Permalink
Ive tried to install concrete5 on my server but it says it has to be PHP5 now I've looked at my hosting specs and to do this I have to have .php5 not .php but that involves changing all the coding and file names for concrete5 is there an easier option?
Thanks
Thanks
the version of php shouldn't have to be in the extension... your webhost is running php4 and php5 on the same machine??
PHP4 and 5 can co exist and operate simultaneously in a Linux environment. You do not have to remove php4 in order to use php5, the handlers are just mapped to the different Apache modules by x-map. The two versions can co-exist and apparently can both be loaded into the apache run-time environment. Each version of the engine has a separate set of libraries that are not shared as well as separate ini files and apache modules. The server checks the file extension and then chose one of the slotted editions of the engine based on the file extension. In this case what basically happens is the server reads the .htaccess file in the parent folder and when it does, the .htaccess file overrides the server default and tells the server that it should map .php to .php5. So when the server accesses the .php files, in for example, concrete it effectively sees .php5 and routes it to the appropriate module.
It is very common on linux hosting for this to be the case as php4 is still considered the more stable option. I don't know why, but it is the method that a large number of hosting solutions have chosen. I think this has much more to do with allowing sites coded in php4 to continue to operate appropriately, in other words, it doesn't break half a million customers websites with the roll out of a new language revision. Thus the reason for using addhandler, x-map, and version slotting.
I would prefer that php5 be the only engine, or atleast by the primary engine forcing php4 to use x-mapping but since it is an option on linux based hosting to allow both, outside of security there isn't much of a reason not to offer it. Since users are jailed in this case with an individual uid and guid there isn't much you can do if anything outside of your individual document root afaik.
It is very common on linux hosting for this to be the case as php4 is still considered the more stable option. I don't know why, but it is the method that a large number of hosting solutions have chosen. I think this has much more to do with allowing sites coded in php4 to continue to operate appropriately, in other words, it doesn't break half a million customers websites with the roll out of a new language revision. Thus the reason for using addhandler, x-map, and version slotting.
I would prefer that php5 be the only engine, or atleast by the primary engine forcing php4 to use x-mapping but since it is an option on linux based hosting to allow both, outside of security there isn't much of a reason not to offer it. Since users are jailed in this case with an individual uid and guid there isn't much you can do if anything outside of your individual document root afaik.
Take a look at this help page and you might be able to apply the same method on your hosting service, so long as they support the use of .htaccess files.
http://faq.1and1.com/scripting_languages_supported/php/9.html...
I guess I should note, I use linux hosting and not windows hosting. As that is an important factor in my case.