removing index.php messing up site
Permalink
I have installed C5 successfully and when I go to system settings and "remove index.php" then the site gets completely messed up. At that point I go back to the home page and from there I can't go anywhere, not even back to the dashboard. I have installed C5 many many times and have removed index.php and have never had this issue.
It should tell you the .htaccess code to put in in the root of your website. Version 8 doesn't install that code automatically for some reason.
My bad, I didn't mention that this is 5.7.5.13
I just did an install last week and had no problems, but it was a different server.
I just did an install last week and had no problems, but it was a different server.
A few things to check
1) You should be able to access any page by manually typing index.php as the first part of the path of the url, e.g.www.www.example.com//index.php/dashboard/.... Assuming you can, try clearing and disabling the cache - particularly if full page caching is enabled.
/index.php/dashboard/system/optimization/cache
index.php/dashboard/system/optimization/clearcache
2) Has the .htaccess file actually been written or uploaded to the site's document root?
3) Does this server actually support mod_rewrite?
4) Does this server allow the processing of .htaccess files? An easy way to find out is to replace .htaccess with some other text file containing any old rubbish. If it is processing them, you should receive a 500 server error because the file will now have incorrect information in it.
1) You should be able to access any page by manually typing index.php as the first part of the path of the url, e.g.www.www.example.com//index.php/dashboard/.... Assuming you can, try clearing and disabling the cache - particularly if full page caching is enabled.
/index.php/dashboard/system/optimization/cache
index.php/dashboard/system/optimization/clearcache
2) Has the .htaccess file actually been written or uploaded to the site's document root?
3) Does this server actually support mod_rewrite?
4) Does this server allow the processing of .htaccess files? An easy way to find out is to replace .htaccess with some other text file containing any old rubbish. If it is processing them, you should receive a 500 server error because the file will now have incorrect information in it.
