peterhadorn

We did maintain the comments, but it inserted its code again anyway and overwrote several lines of the original htaccess, that’s why a 500 error was caused. This was the first part of the original

RewriteEngine On
RewriteCond %{ENV:HTTPS} on
RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

php_value allow_url_fopen On

<FilesMatch “\.(ttf|otf|eot|woff)$”>
<IfModule mod_headers.c>
Header set Access-Control-Allow-Origin “*”
</IfModule>
</FilesMatch>

Options -Indexes

…and these were the same lines after the WooCommerce update, partially overwritten:

RewriteEngine On
RewriteCond %{ENV:HTTPS} on

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
h>

Options -Indexes

I understand it’s not really a WooCommerce issue, but how can this ever happen (original WP code with comments is further down in this htaccess)?

Just had the same issue with the update to WooCommerce 2.4.4. It screwed up the custom .htaccess on that site. We could fix it easily by replacing it with a backed up version. Why would a WooCommerce update need to trigger a permalinks refresh with rewriting htaccess? The admin can do that manually if needed?

Thanks a lot, works like a breeze 🙂