CI -index.php?

[eluser]dijon[/eluser]
thanks.

[eluser]unsub[/eluser]
Hi
wow, I'm so close, css and images are back now, as is js, but now I'm getting the same issue as the first poster, ie: when I drop the index.php it redirects to my default controller. So now I'm going to try the other uri protocols to see if they work.

Thank you so much for your help on this. I was ready to just give in and not use pagination, haha.
Looks like I have a lot of reading to do to understand htaccess.

cheers
-gabriel

[eluser]unsub[/eluser]
woohoo

request_uri protocol works like a charm with this htaccess configuration.

Thanks a million.

[eluser]m40[/eluser]
But why isn't index.php hidden by default? Why would anyone use index.php based URLs?

[eluser]Twisted1919[/eluser]
[quote author="m40" date="1249358942"]But why isn't index.php hidden by default? Why would anyone use index.php based URLs?[/quote]
Index.php acts as the front controller to the whole site .
Even if you use mod rewrite , this doesn't mean that all the requests will not pass through index.php , because they will .
At least this is what i understand from user_guide .

[eluser]Colin Williams[/eluser]

But why isn’t index.php hidden by default? Why would anyone use index.php based URLs?

Not all server configurations allow for something like mod_rewrite. On one hand it would be nice if CI shipped with a .htaccess.dist file with all rules commented out. The example in the user guide is okay but the one in the Wiki is better. This probably isn't going to end the questions because, sadly, not a whole lot of new developers take the time to learn about their server software. They just copy/paste stuff until it "magically" works. But, it would at least keep users from going through the motion: Go to user guide, find example mod_rewrite rules, implement rules, have their images/css/js "disappear", come back to forums, and on and on...