Breaks multisite

Hello

i have a similar problem. No 404 error though, no slow backend.
But all images, CSS and JS files result in error 500.
Which obviously makes Wordfence unusable on a multisite installation.

However, this seems to be due only to the way the .htaccess in the plugin folder is written.
Still trying to find out how to correct the order directive which seems to be causing the problem on my GNU/Linux Apache webserver.

Ok, well. The .htaccess of wordfence protects some screenshots (not really useful i think) and the readme.txt (useful because this hides the version of wordfence) and also the .htaccess (not useful, because this file is protected from being read by default, at least on a basic Debian/Apache installation).

As this .htaccess does not protect any other files as these, what you can probably do is just remove the .htaccess file and rename the readme.txt.

Does anybody have an opinion on this ?

I′m digging my error-logs on my multisite, trying to find out where the errors pointing to my themes css/images folder are coming from and found this thread here.
“As this .htaccess does not protect any other files as these, what you can probably do is just remove the .htaccess file and rename the readme.txt.” –>
Can this be done without downsides?
Any news on this, please?

Hi Guys,

We’re ditching that .htaccess because it doesn’t serve any useful function in the next version.

Let me know if I can help further.

Regards,

Mark.

@siga : in my opinion there is no downside, as long as you rename the readme.txt.

@Wordfence : great news ??