Thread

Why exactly does the URL structure appear this way?

http://mtharmony.org.s30200.gridserver.com/index.php/site/visitors/

The part I am referring to is the part after the “.com”.

Is there a way to control this?

Greetings, venti - index.php is the gateway through which the server knows that ExpressionEngine is being called; it can be removed, on some servers (and the removal is not officially supported) by using one of the methods in this wiki entry.  Beyond that, please read Understanding URLs and the Importance of Semantics

Thank you very much. I’ll look over the links.

Do you know if by chance Media Temple’s Grid Service supports the removal?

And do you know if this URL structure effects Google Analytics tracking?

Thank you again.

Bryan

It does not effect Google Analytics; I’ve never used MT’s Grid Service, but I believe some people are using that method on those servers. If they support .htaccess mod_rewrites you should be good to go.

hi ventistudios,

yes, mediatemple supports the index.php removal with .htaccess rewrite mode. This one is tested and works:

RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ /index.php?/$1 [L]

just paste these 4 lines into your .htaccess file in the root of your webserver

Greetings, venti - index.php is the gateway through which the server knows that ExpressionEngine is being called; it can be removed, on some servers (and the removal is not officially supported) by using one of the methods in this wiki entry.  Beyond that, please read Understanding URLs and the Importance of Semantics

Lisa, I have seen you mention this “is not supported” a few times.  Is this because you have seen problems doing this, or just because it wasn’t intended that way and you don’t want to have to support different server configurations to make it happen?

Any plans to make it an option in the future?  It would be a great feature for people who have already established links, or prefer the standardized look (and considerably easier explaining the url verbally to our clients) of it.

Hi Saxi,

Its not officially supported because its not part of EE’s code. As you can see by browsing the forums we often help with this. Its unlikely that this feature will ever be included directly in EE due to the vast variety of sever configurations and setups.

Is the main reason because of the vast amount of setups and the fact its configuration always depends on outside influences, or are their particular issues we might run into using it, I am very interested in doing this as I am not a fan of the /index.php/path idea, but I don’t want to introduce problems.  Although I see a lot of EE installations using it so it sounds safe.

Is the main reason because of the vast amount of setups and the fact its configuration always depends on outside influences, or are their particular issues we might run into using it, I am very interested in doing this as I am not a fan of the /index.php/path idea, but I don’t want to introduce problems.  Although I see a lot of EE installations using it so it sounds safe.

You’re correct on both counts though the majority of people using the .htaccess method don’t experience issues. Just be careful and if you run into problems post and you’ll very likely get good feedback.