<p>Have you seen this on the Craft site: <a href="http://buildwithcraft.com/help/why-index.php" rel="nofollow">http://buildwithcraft.com/help/why-index.php</a> ?</p>

CC BY-SA 3.0
2015-06-01T18:10:00.007Z
yes, I've tried this, I mentioned it in my post.
Samsull
CC BY-SA 3.0
2015-06-07T11:08:02.307Z
This post has NOT been answered. I can only find a temporary fix.
Samsull
CC BY-SA 3.0
2017-12-19T16:57:33.540Z
I have the same issue as described here. Stumped.
SoHo
CC BY-SA 3.0
2015-06-01T10:19:41.013Z
2015-06-01T10:19:41.013Z
Wolfram Gehring
<p>I can't get rid of that pesky index.php?p= from my urls.</p>

<p><a href="http://mysite.com/index.php?p=about/people" rel="nofollow">http://mysite.com/index.php?p=about/people</a></p>

<p>If I manually remove index.php?p= e.g. <a href="http://mysite.com/about/people" rel="nofollow">http://mysite.com/about/people</a> it works, but then goes back to adding the index.php?p= as soon as I navigate away.</p>

<p>I've tried adding 'usePathInfo' => true, and 'omitScriptNameInUrls' => true, to general.php</p>

<p>PathInfo works, <a href="http://mysite.com/index.php/testPathInfo" rel="nofollow">http://mysite.com/index.php/testPathInfo</a> = 'success'</p>

<p>When I add garbage to htaccess I get server error, so htaccess works.</p>

<p>And I have another site with a very similar build on the same server that's working fine.</p>

<p>Is there anything else I can look at?</p>

CC BY-SA 3.0
2015-05-29T09:51:20.740Z
Have you checked to make sure `index.php?p=` isn't actually present in you `siteUrl` config variable?
Alec Ritson
CC BY-SA 3.0
2015-05-29T17:28:50.517Z
I'm using baseUrl with {baseUrl} in Site URL in general settings, and no index.php?p= present.
Samsull
CC BY-SA 3.0
2015-05-29T17:36:00.860Z
Is this a vanilla Apache install?
Brad Bell
CC BY-SA 3.0
2015-05-31T12:09:40.350Z
It's on a new VPS and I've added the missing extensions to get Craft up and running. For another site on the exact same server I'm not seeing the rogue index.php
Samsull
CC BY-SA 3.0
2015-06-04T13:22:20.283Z
If I avoid using the url link e.g. {{ aboutUs.url }} it gets rid of the index.php. For example, this works: <a href="{{ siteUrl }}about-us/{{ aboutUs.slug }}">{{ aboutUs.title }} and this doesn't: <a href="{{ aboutUs.url }}">{{ aboutUs.title }}</a> . It works by splitting up the url with a slug variable.
Samsull
<url>
Another index.php?p= problem
# Another index.php?p= problem

(Asked by: username_0 on 2015-05-29)

I can't get rid of that pesky index.php?p= from my urls.

<http://mysite.com/index.php?p=about/people>

If I manually remove index.php?p= e.g. <http://mysite.com/about/people> it works, but then goes back to adding the index.php?p= as soon as I navigate away.

I've tried adding 'usePathInfo' => true, and 'omitScriptNameInUrls' => true, to general.php

PathInfo works, <http://mysite.com/index.php/testPathInfo> = 'success'

When I add garbage to htaccess I get server error, so htaccess works.

And I have another site with a very similar build on the same server that's working fine.

Is there anything else I can look at?

**Tags:** url
> **Comments:**
> **username_1**: Have you checked to make sure `index.php?p=` isn't actually present in you `siteUrl` config variable?  
> **username_0**: I'm using baseUrl with {baseUrl} in Site URL in general settings, and no index.php?p= present.  
> **username_2**: Is this a vanilla Apache install?  
> **username_0**: It's on a new VPS and I've added the missing extensions to get Craft up and running. For another site on the exact same server I'm not seeing the rogue index.php  
> **username_0**: If I avoid using the url link e.g. {{ aboutUs.url }} it gets rid of the index.php. For example, this works: <a href="{{ siteUrl }}about-us/{{ aboutUs.slug }}">{{ aboutUs.title }} and this doesn't: <a href="{{ aboutUs.url }}">{{ aboutUs.title }}</a> . It works by splitting up the url with a slug variable.  

---

## 1 answers

### Answer by username_3 on 2015-06-01. Score: 1

Have you seen this on the Craft site: <http://buildwithcraft.com/help/why-index.php> ?

> **Comments:**
> **username_0**: yes, I've tried this, I mentioned it in my post.  
> **username_0**: This post has NOT been answered. I can only find a temporary fix.  
> **username_4**: I have the same issue as described here. Stumped.  

---

