“concrete5 cannot parse the PATH_INFO or ORIG_PATH_INFO information provided by your server.”

Thought I’d take a look into concrete5 to see what is was like, and it’s the first open source PHP project installer I’ve come across in ages that complained about anything other than filesystem permissions. PATH_INFO? Most other projects use different mechanisms/variables to do a similar job I assume…

Anyways, go to the concrete5 install directory and create a .htaccess file there with the following contents:

php_flag display_errors off
AcceptPathInfo On

If you don’t suppress PHP errors it won’t work, which I read may be related to an Ajax callback failing because the response is full of errors (the installer isn’t written properly? I’ve no idea…)

I’ve also heard that some hosting providers (like GoDaddy) don’t play well with .htaccess files, which unfortunately if that’s the case you’ll have to get in touch with them!

1 comment

  • Oh man!!! Fighting for weeks getting some domains migrated from a wheezy build to a jessie rc1 build, could not get pretty URLS to play nice no matter what, until I found your tip on customizing the .htaccess contents. Oh yeah baby!!! Now I can get on with migrating my sites off my geriatric PowerEdge T605 to an underprocessored HP MicroServer, woohoo!!!