Install issues / FastCGI / Modifying the core
Permalink
Had lots of trouble getting Concrete5 to run on our hosting account.
Basically, the mod_rewrites were not working correctly even though the module was loaded and running correctly. Basically none of the links worked and could not even log into Concrete5.
Anyway, the hosting company partially sorted it out and it almost works fine - except I am really concerned about their changes.
They modified a core file /concrete/libraries/request.php.
They changed line 72 from:
To:
Also, they changed the .htaccess file to:
I'm not so concerned about the .htaccess file, but more so the changes they did to the core.
As it stands, the changes they did solved the problems and the site is now loading correctly and I can access all page, and I can finally login to the cms.
However the "sitemap" (via the dashboard) no longer works anymore, I now get a 404 error.
This renders Concrete5 useless now since I cannot navigate to the page I want to edit via the sitemap.
I'm concerned that the changes they made have in fact broken the sitemap and possible other things I'm currently unaware of.
They tell me that Concrete5 is not designed to work with FastCGI which their servers are running. Therefore these changes they did enable Concrete5 to run on their servers.
Is this the right way to get Concrete5 to work? and why cant I access the site map anymore?
Basically, the mod_rewrites were not working correctly even though the module was loaded and running correctly. Basically none of the links worked and could not even log into Concrete5.
Anyway, the hosting company partially sorted it out and it almost works fine - except I am really concerned about their changes.
They modified a core file /concrete/libraries/request.php.
They changed line 72 from:
$path = Request::parsePathFromRequest('ORIG_PATH_INFO');
To:
$path = Request::parsePathFromRequest('REDIRECT_URL');
Also, they changed the .htaccess file to:
<IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule .* index.php/$1 [L] </IfModule>
I'm not so concerned about the .htaccess file, but more so the changes they did to the core.
As it stands, the changes they did solved the problems and the site is now loading correctly and I can access all page, and I can finally login to the cms.
However the "sitemap" (via the dashboard) no longer works anymore, I now get a 404 error.
This renders Concrete5 useless now since I cannot navigate to the page I want to edit via the sitemap.
I'm concerned that the changes they made have in fact broken the sitemap and possible other things I'm currently unaware of.
They tell me that Concrete5 is not designed to work with FastCGI which their servers are running. Therefore these changes they did enable Concrete5 to run on their servers.
Is this the right way to get Concrete5 to work? and why cant I access the site map anymore?
Read this http://www.concrete5.org/developers/bugs/5-4-1-1/path_info-problem/...
Ok this link you sent mentions the same sort of thing. Basically it's says to update the file /concrete/libraries/request.php.
I have applied the change as suggested in the post, and it will only work if the .htaccess changes I mentioned above have been applied.
However, I still cannot access the sitemap. I still get 404 error.
The link you sent mentions this fix has been applied in the next versions of concrete, but if the fix is exactly as it was documented in the post, then it doesn't solve my particular problem.
