Let’s see if this is ab it more helpful for you.
I’ve activated Your plugin. Apache starts giving me the following error.
[Sat Oct 10 14:33:53.866214 2015] [core:alert] [pid 2924] [client 148.101.11.104:55132] /var/www/wp-content/plugins/wp-admin-bar-removal/.htaccess: DirectoryIndex not allowed here, referer: http://example.com/wp-admin/plugins.php?deleted=true&plugin_status=all&paged=1&s=
Decided checking out the following file, due to the error message above:
/var/www/wp-content/plugins/wp-admin-bar-removal/.htaccess
I commented the following line, since it seems to be the source of the problem.
DirectoryIndex index.php /index.php
The error changed to this:
[Sat Oct 10 14:32:43.120331 2015] [core:alert] [pid 2870] [client 148.101.11.104:22285] /var/www/wp-content/plugins/wp-admin-bar-removal/.htaccess: Invalid command ‘Header’, perhaps misspelled or defined by a module not included in the server configuration, referer: http://example.com/wp-admin/plugin-install.php
Any ideas on what can be causing this?
Plugin Contributor
slangji
(@slangji)
cardpogi wrote: any ideas on what can be causing this?
Yes: WordPress for Dummies
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@slangji Your contributions to this topic have been limited.
Very good spam! !!
and
cardpogi wrote: any ideas on what can be causing this?
Yes: WordPress for Dummies
Is that really useful? You don’t have to provide support here but please treat all the members here with respect.
*Looks, installs plugin on test setup*
@cardpogi It looks the file .htaccess in that directory is causing you grief.
https://plugins.trac.wordpress.org/browser/wp-admin-bar-removal/trunk/.htaccess
Either delete that file or rename it to something else so it does not get parsed. I vote for deleting.
Thank you
@ Joan Dembowski worked wonders
Plugin Contributor
slangji
(@slangji)
Deleting .htaccess expose plugin and WordPress to related security issues: the author of this plugin can not be held responsible in this regard.
Refer to delete a file of a plugin, it is advice that a moderator should not do, because beyond its role, not knowing the reasons for its existence within the plugin itself.
If “cardpogi” real need assistance please visit https://slangji.wordpress.com/support/premium-support/ because is written clearly that sLaNGjIs team do not providing support on wordpress.org forum and continue to register users, with false issues, is not the way.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Thanks for chiming in positively.
Deleting .htaccess expose plugin and WordPress to related security issues: the author of this plugin can not be held responsible in this regard.
I don’t expect that any author would. Also I run nginx and I take security very seriously. That .htaccess file is unnecessary IMHO. And in at least one Apache2 setup is needlessly causing those warning log entries.
Your plugin shouldn’t need that file. It’s nice that you are security minded but it’s your code that has to be up to muster.
NOTE: I am not saying that your code is not secure.
and continue to register users, with false issues, is not the way.
Hands down, this was 100% not a false issue and your plugin’s .htaccess file was responsible for that.
Plugin Contributor
slangji
(@slangji)
That .htaccess file is not unnecessary IMHO.
cardpogi run apache not nginx! !!
But you do not know:
1 – What version of apache run
2 – What version of the plugin run
3 – What’s in that file .htaccess
4 – How it was commented …
5 – And more other informations to goal any good support
As you can to support this: random?
Guessing, like magicians, configurations of possible users?
… And do not add more! !!
Plugin Contributor
slangji
(@slangji)
Jan Dembowski wrote:
Hands down, this was 100% not a false issue and your plugin’s .htaccess file was responsible for that.
I know my plugin, and i know even better that error message, “header” that is not caused by the .htaccess file.
Then each one think what he wants.
P.S. To be precise: it not received any official request, to my support, as part of this “user”.
