Thread

Frankly, many people abhor index.php. Also the fact that pretty much every template name takes a url segment (index.php/blog/comments/title, index.php/blog/category/C1) is not so great IMO.

I know that as developers we’re all very url conscious.  A lot of people that aren’t involved in web-development couldn’t care less.  Index.php aside, I’m curious how you imagine the reduced url segments should look.  What would you rather see instead of /blog/comments/title?

I think what duke is saying is that /blog/comments/title is fine… but index.php/blog/comments/title is not. The previous host I used had a lot of issues with EE and .htaccess and that is why I delayed moving to EE for so long because I couldn’t remove index.php.

Also, I would like to note an entry by Derek Jones located here: a present for your friday

... ExpressionEngine 2.0 is primarily about the technology leap being made with respect to its architecture (running on CodeIgniter), and a complete overhaul of the control panel UI.  That’s no small thing of course, as that means both the server side and client side code are changing dramatically, even if there aren’t any new features to add to a particular process.  But we still have a number of tricks up our sleeve for you that we think will revolutionize your workflow when building and maintaining sites.  I leave you today with one such nugget, a small insignificant thing, but something we think will be quite helpful and a time saver during the install process.

Saying that the option to remove index.php at the install, see the link above for the graphic, is not possible or a “high priority” is kinda nuts. It is a hot topic, I have looked for sites in the showcase that had index.php and i don’t recall seeing any that used index.php in the URL.

BTW - EE techs and engs are in fact “freaks of nature”, in my book, when it comes to creating a beautiful CMS that is incredibly stable and well though out!

Saying that the option to remove index.php at the install, see the link above for the graphic, is not possible or a “high priority” is kinda nuts. It is a hot topic,

Its level of desirability is rather immaterial.  If we can’t control your server environment, we can’t guarantee any of our efforts toward this end will work, no matter how high of priority we assign it.

I have looked for sites in the showcase that had index.php and i don’t recall seeing any that used index.php in the URL.

Two very high profile and traffic sites from the top of my head:
http://ilounge.com/
http://macdailynews.com/

I still don’t get it. If it bothers you so much, remove it and move on. If your hosts supports it, you can do it. It it doesn’t, EE couldn’t either.

Its level of desirability is rather immaterial.  If we can’t control your server environement, we can’t guarantee any of our efforts toward this end will work, no matter how high of priority we assign it.

How feasible would it be to do a check of the server environment and give this as an option if the host has the necessary requirements?  Or, less desirable but better than nothing, how about a tie-in with EngineHosting?  Host with EH and this is an option during install?

Thanks for being so open to community ideas :roll:

I personally don’t like to delve into unsupported hacks on sites I make. I’ve found over the years that it usually comes back to haunt me in some fashion.

EDIT:  Oops - looks like Ingmar deleted his post.  I was referring to this:

I still don’t get it. If it bothers you so much, remove it and move on. If
you hosts supports it, you can do it. It it doesn’t, EE couldn’t either.

If I could change the topic title to “Plans for no index.php install option for EE 2.0?” I would

Wouldn’t that save time as stated in your blog? It isn’t hard or very time consuming, but it would be very convenient to quite a few people.

Maybe a better idea would be to have an option at the install screen that would test to see if the .htaccess method would work on the server of installation and then if successful give you the option to install the automatic .htaccess method for you. I am sure it would be some work and I am definitely not an expert, I am just trying to make a suggestion.

I didn’t refresh, I agree with Brian.

Thanks WTHIGO? for bringing this up.

For me as a non-geek easy index.php dropping from url would be a much desired feature.

[...]

How feasible would it be to do a check of the server environment and give this as an option if the host has the necessary requirements?  Or, less desirable but better than nothing, how about a tie-in with EngineHosting?  Host with EH and this is an option during install?

Good idea Brian. That would be better than nothing.

Brian, It’s nice to know that other people have the same idea about the index.php

Leevi Graham has come up with an GREAT extension for generating the .htaccess!

http://ellislab.com/forums/viewthread/90365/

http://leevigraham.com/cms-customisation/expressionengine/lg-htaccess-generator/

Leevi Graham has come up with an GREAT extension for generating the .htaccess!

http://ellislab.com/forums/viewthread/90365/

http://leevigraham.com/cms-customisation/expressionengine/lg-htaccess-generator/

Thanks for the shout-out… So much for the quiet soft launch :p

Hope you all enjoy it and don’t forget to bookmark it and share on your social networks!

Cheers Leevi

Sorry, saw it on Twitter and the Extensions Forum… IM A JERK! MY BAD :cheese:

I am relatively new to EE and am somewhat oblivious to it’s internal machinations.
Yet I find the index.php in the url unwelcome and want to get rid of it.

So I spent the last 5 hrs trying the LG .htaccess plugin and then, when I couldn’t get that working, trying in vain to rename index.php

I’ve done it before on another site so I know it’s do-able.
Yet I’ve looked researched, double-checked, tested options to no avail.
now I’m burnt out and unhappily back to index.php

This “hack” is not nearly as dismissively simple or transparent as some earlier replies would suggest.
Especially to a relative noob (.htaccess and php commands are greek to me)
ExpressionEngine is supposed to be accessible to the layman.
and I consider pretty urls a core feature.

both this thread and the LG generator thread have 2000+ views each.
Surely this indicates a broader frustrated need.

I would like to see this addressed in 2.0 with a control-panel option
(for re-naming at least)

-Thanks

I’ve done it before on another site so I know it’s do-able.

Yes, but much depends on your host, your setup & environment. It won’t work in all situations.

This “hack” is not nearly as dismissively simple or transparent as some earlier replies would suggest.

It’s not a hack, really, but using URL rewriting. And while this will work in many cases, it is a semi-advanced issue and we really cannot officially support it, as it won’t work in all situations and there’s nothing we can do about it.