I’ve used Local to develop around ten websites. I just created a new site in the same exact method I’ve used every single time, and I now have index.php in my permalink structure (ex: “http://website.dev/index.php/sample-post/”). I don’t understand where this came from, why it happened (which is the most important thing I’d like to know), though I have found articles on how to potentially remove this (by editing the .htaccess file). It’s fine if that works, but why did this happen suddenly? I would really like to know if anyone else has this problem or had this problem with a Local site build.
Thanks so much for your time and any explanation and assistance.
I did actually go into the Permalinks settings and deleted the /index.php/ portion out of the Custom Structure option, and it appears to be working. If that works, that’s great, I just tend to get a little worried because I don’t understand why this is happening in the first place.
I created another site quickly using the preferred setup, and each time it is adding the index.php into the permalink structure…weird.
Having the same issue here. In my case, I’ve found that removing /index.php/ from the Custom Structure will resolve the issue to a certain extent. However, /index.php/ is still displayed within the permalink options for all of the other Custom Settings and if I switch to any of these other options (eg. Day and name) the problem persists.
I hopped into Sequel Pro and examined the Content / wp_options and noticed that the permalink structure is set to /index.php/%year%/%monthnum%/%day%/%postname%/
I’m still somewhat new to making these sorts of direct changes to the database, but attempted to remove /index.php/ and OK the changes. Somehow, it’s still being added back in. Any suggestions?
If you’re having this issue, try adding the following to the wp-config.php file above the /* That's all, stop editing! Happy blogging. */ line:
if (strpos($_SERVER['SERVER_SOFTWARE'], 'Flywheel/') !== false) {
$_SERVER['SERVER_SOFTWARE'] = 'nginx/1.10.1';
}
Local 2.1.2 will address this issue by automatically inserting that snippet for any site using the Preferred environment. In the next update of the Preferred environment we’ll be removing the custom SERVER_SOFTWARE param in the nginx config.