PATH_INFO and ORIG_PATH_INFO

Permalink
Hi all

Great CMS, definitely developed on a MAC. I am envious. ANYWAY, I am trying to install this on shared hosting (I know I know, host with concrete and I won't have this issue) and the client doesn't want to switch hosting.

Everything appears to load fine on the main install page and throws this exception "Concrete cannot parse the PATH_INFO or ORIG_PATH_INFO information provided by your server." Which files want to read this since I know it is looking for my complete path. I was trying to search the directory structure last night and my eyes didn't want to work right. Can anyone help me out?

(reading several posts on this "installation forum), one question I am assuming the answer on is that "The "site.php" file is created once the installation script has run. Am I correct on this?")

Bill

bcarone
View Replies:
Remo replied on at Permalink Reply
Remo
it's not a file, do this to check path_info support:

1. create a file containing this code
<?php
phpinfo();
?>

2. save it as info.php
3. open it using any browser, should work.
4. open it again but this time, append something to the url like this "info.php/myPathInfo", this must work too!
5. output must contain myPathInfo

if it doesn't, you're using a pretty bad hosting provider that won't support concrete5, nor wordpress and a few other systems....
bcarone replied on at Permalink Reply
bcarone
Remo I had already run a PHPINFO script and it reads it fine. Since my hosting service allows me to run WORDPRESS and JOOMLA and VANILLA and a host of other PHP scripts I do know my provider pretty decently. Suggesting that I run PHPINFO is a standard response and doesn't tell me anything to check for.

I do know a SMALL amount of PHP but I didn't think I would have to start getting into the nitty gritty of the way c5 operates just to load it and take it for a test spin. I find the features that I have seen and looked at on the tutorials unique in several ways and would really like to show this to my clients. It has a small footprint and very small learning curve once it installs properly. SO DON'T ASSUME it is a "hosting" problem. It just may be an issue in the way it installs on different platforms.

But thank you for your response.
bcarone replied on at Permalink Reply
bcarone
OK folks......

1. for hosting on GoDaddy, Andrew had a work around posted on the BUGS forum, took me awhile to find it. It was for version c5.1.x but still applies with c5.2.x (http://www.concrete5.org/community/bugs/fixes/patch_godaddy_hosting)

2. Godaddy is looking at the script at a 2-3 level to make sure c5 will install easily without this patch. Will know in a day or so.

3. IF you only register your domain at godaddy and opt to have their free web site tonight page, YOU WILL NOT BE ABLE TO RUN C5 on it. I verified with GoDaddy about this.

Andrew, thanks for your email. I will email a more detailed version of the fix.

Bill
davidgiffon replied on at Permalink Reply
The server isn't the problem here either... I've tried everything on this page and others and still get this same message. >I've tried other cms apps and they work fine. I'd really like to get to the next stage instead of staying and losing an entire day on trying to get past PAGE_INFO etc.

Please help!
frz replied on at Permalink Reply
frz
page_info and orig_path_info errors could happen for any number of different reasons on install. Can you post a php info call so people can actually look at your configuration, or did i miss that?
funby15 replied on at Permalink Reply
i tried creating info.php it works fine then whats the prob

try funby15.xtreemhost.com/info.php (php info)

funby15.xtreemhost.com (my site with errors)
Remo replied on at Permalink Reply
Remo
yes, path_info works fine on your server but putenv doesn't.

The ajax script which checks whether path_info works or not gets this result:
<br />
<b>Warning</b>:  putenv() has been disabled for security reasons in <b>/home/vol2/xtreemhost.com/xth_4753168/htdocs/concrete/libraries/localization.php</b> on line <b>33</b><br />
{"response":40}


Because of the warning it isn't able to parse the response correctly.

You can modify php.ini to hide warnings or try to enable putenv..