“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!
Leave a comment
Categories
- Nagios is a blessing and a curse...
- RT @kiyanforoughi: Yoko Kanno is simply... wow....
- RT @fransgaard: OCP anyone? Call Robocop: BBC News - Private security firm G4S to run Lincolnshire police station http://t.co/Ek6KS1aV
- Update schema.xml, commit to repo, update Puppet, run Puppet, restart Tomcat, reindex Solr, realise it doesn't work, rinse-repeat...
- To all broadcasters, READ THIS and LEARN FROM IT http://t.co/7KBeCpK9 #piracy
Recent Posts
- “concrete5 cannot parse the PATH_INFO or ORIG_PATH_INFO information provided by your server.”
- Enable hibernation on HP MicroServer for Windows Home Server v1
- VirtualBox Guest Additions with Shared Folders on Mac OS X
- Using PHP late static binding to define static arrays as subsets for child classes
- MySQL socket missing at /tmp/mysql.sock with Zend Server CE on Mac OS X




