Why do URL paths have "index.php" before SEO-friendly URLs?
Permalink 1 user found helpfulhttp://php.22graphics.com/print/collateral-sessanta-60...
But, those don't work at all. It only works if you put an "index.php" in between "22graphics.com" and "print" like so:
http://php.22graphics.com/index.php/print/collateral-sessanta-60...
I find this very annoying and I think something is wrong with my set-up, but I don't know what.
But for some reason my PREVIOUS and NEXT buttons don't seem to be following suit. They still stick in the "index.php"
I embedded them in my template with this code:
<?php $bt = BlockType::getByHandle('tony_next_previous'); $bt->controller->nextLabel = 'Next'; $bt->controller->previousLabel = 'Previous'; $bt->controller->showArrows =1; $bt->controller->loopSequence=1; //$bt->render('templates/footer_bar'); $bt->render('view'); ?>
Any idea what I need to change to make them show Pretty URLs?
You should be able to force Concrete to never include it in your links by adding this line to your /config/site.php file:
define("URL_REWRITING_ALL", true);
Just be aware that if URL rewriting is not working, you will have great difficulty accessing your dashboard or other pages. Remember that this is in your site.php file, and you can disable the setting if necessary. However, with everything working fine, you can enable this and (hopefully) have it drop out of all your links
Thank you, it is nice to know how to fix it!
Here's a quote from the documentation:
"To enable Pretty URLs, login to your concrete5 instance as the Admin user, and goto Dashboard > Sitewide Settings. There's an option on the right of that page which you can turn on. You may also have to create a .htaccess file on your sever for this to work right, the Dashboard will provide the details for that file."
http://www.concrete5.org/documentation/installation/installing_conc...
In reality, everything is passing through that index page, because the files and pages don't actually exist on the server. Instead, it passes through Concrete, which understands what that URL means. By using URL rewriting, you're able to instruct the server to send the path through Concrete rather than providing a page not found error.