vvandens on "[Plugin: iThemes Security (formerly Better WP Security)] Plugin creates error in .htaccess file not allowed"

ساخت وبلاگ

NuttyHiker
Member
Posted 3 months ago #

AH00526: Syntax error on line 8 of /home/xxxxxx/public_html/.htaccess:
<RequireAll not allowed here Please try again.)

https://wordpress.org/plugins/better-wp-security/

@NuttyHiker

This is not the right forum to post an error due to an Apache configuration issue ...

I'm assuming the line:

<RequireAll not allowed here Please try again.)

contains 2 typos and should instead be:

<RequireAll> not allowed here Please try again.

Google a bit and hike your way to a place like this.
Or alteatively contact your hosting provider.

This is not an iTSec plugin error so please mark this topic as 'resolved'.

dwinden

NuttyHiker
Member
Posted 3 months ago #

Um excuse me, but it's this plugin that is causing the error in the .htaccess file so yes it is the right forum to post the error. And I did contact my hosting provider, which is why I am here.

More specifically when you check the setting Enable Ban Users. It inserts that code when that setting is checked. When you uncheck the setting it removes that code. So yes it is the plugin that is creating it! The .htaccess file does not have those typos. It has <RequireAll>

@NuttyHiker

I don't remember saying the iTSec plugin did not create that line in the .htaccess file ... I actually agree that it does.

What I'm saying is that it is an Apache configuration error.
It's not an iTSec plugin error.

Your website is not just the iTSec plugin ...
There is a webserver (Apache), PHP, MySQL, WP, iTSec plugin ... and more.
All working together.

The .htaccess is a file that is closely working together with the webserver (Apache).
If your hosting provider is not able to help you solve this Apache configuration error I guess it's time to look for a different hosting provider ...
(Trying to push you in the right direction ...)

dwinden

@NuttyHiker

If you require no further assistance please mark this topic as 'resolved'.

dwinden

vvandens
Member
Posted 4 minutes ago #

@NuttyHiker

I had the same problem on my Apache 2.4 server.
You have to allow AuthConfig to be overridden in your site configuration for the IT sec .htaccess modified file to be valid.
My configuration looks like this :

<Directory /path/to/my/site> Options Indexes FollowSymLinks MultiViews AllowOverride FileInfo Options Limit AuthConfig Order allow,deny allow from all
</Directory>

- - , .

WordPress ...
ما را در سایت WordPress دنبال می کنید

برچسب : نویسنده : استخدام کار wpss بازدید : 86 تاريخ : يکشنبه 25 بهمن 1394 ساعت: 11:26