My client wanted to find his own host, so I told him to make sure that it had MySQL 4.1+ and PHP 5+.
But I did not know about all the IIS mod_rewrite issues, and he of course found a host that is using IIS (unknown version for the moment)
After copying the Silverstripe (v2.3.3) install files, when trying to access the install.php, I was presented with a "HTTP Error 500".
Thinking it might have something to do with the content of the .htaccess file, I removed its whole content.
This allowed me to install Silverstripe properly. (Although there seem to be know CSS formatting on the install page and the install does stop after # Checking that friendly URLs work... # Testing...)
Afterwards however, the HTTP Error 500 came back.
My understanding is that this would be because the IIS server doesn't have a mod_rewrite enabled.
However, from reading this http://groups.google.com/group/silverstripe-dev/browse_thread/thread/f0c082132f3f1014?pli=1
, I think I understand that I should be able to use it anyway if I remove the rewrite rules from the .htaccess file, which I did.
Did I miss something? Is there something else I am supposed to do to get it working without the pretty URLs?
Anyone has any idea of something I could try?
I thought I might add that the 500 Error seems to come from IISPassword, which according to its makers is "the equivalent of htaccess on Apache, except that itâ€™s used on Microsoft IIS."
I don't know if it's relevant, but I'm wondering if this causes problems, e.g. not allowing access to directories that actually don't exist...