Include .htaccess in distribution

[mikaelstaldal]

It seems like .htaccess looks the same all the time in WordPress 2.x. But it still attempts to update it when the premalink structure is changed.

It would be easier if .htaccess simply was included in the distribution and WordPress doesn't try to write to it.

[JeremyVisser]

You can't really presume the destination server is running Apache or that the filename that the server is looking for has been changed from the default ".htaccess". Or even that .htaccess is enabled on the server, which be default it is not.

I do agree about WordPress not bothering to write to .htaccess if it doesn't need to, though.

[Brian Layman]

I do not agree with this suggestion.

This cause WP to override any .htaccess files that are configured above the WordPress directory. Additionaly, and it will make the upgrade process more difficult as this is a file that could be overwritten very easily when uploading an update. If I lost my .htaccess file, it would require a good bit of scrambling to get the contents restored. (Which reminds me it is time for another backup....)

AFAIK, .htaccess is only created by WordPress if you change your permalink structure. So most installs rely on the .htaccess configured by there web provider. 1and1.com for instance has a special thing for converting the urls to upper or lower case as appropriate. If I put a custem perma link structure, and thus create a .htaccess file, that behavior is lost.

[Nazgul]

The consensus thus far has been that this won't be fixed.

If you have any other suggestions, please feel free to reopen this ticket.