Posted 1 year ago #
I have this error while activating AskApache Password Protect 3.5.1 at WP 2.5:
Fatal error: Cannot redeclare aa_pp_options_setup() (previously declared in /sata1/home/users/ссс/www/www.aaaa.bbb/wp-content/plugins/askapache-password-protect.php:55) in /sata1/home/users/ссс/www/www.aaaa.bbb/wp-content/plugins/askapache-password-protect.php on line 56
Thank you all for ideas and answers!
Posted 1 year ago #
I see exactly the same error when I "activate" the plugin.
Posted 1 year ago #
I am definately thinking it is a WordPress bug. Because its not being redeclared, at least from what I know about redeclaring functions. Its just not.
Maybe the newer AskApache Password Protect 3.6.x version will work for you.
Posted 1 year ago #
First, the plugin is fantastic, but, after upgrade version (3.6.3), i have the same problems described in the comment of the Dmitrius.
Posted 1 year ago #
Same activation error here.
I recently saw this error as well, trying to install it on someone 's blog.
Posted 1 year ago #
same problem here, with aapp 3.6.3, wp 2.5.1 (also with 2.5 previously)
Posted 1 year ago #
I can't figure it out.. sorry.
It doens't make any sense... how can a single add_options_page be declared twice? And why does it say that its occuring on the line right underneath the real one?
I change the name of the option but apparently it is still causing this problem for many.. all with an upgraded version?
..change the name of the option but apparently it is still causing this problem for many.. all with an upgraded version?
I attempted to install 3.6.3 on a 2.5 blog just the other day -- and got exactly that error. Whether or not thats the updated version I don't know. I do know that its the plugin and not me. Ive been doing this for a while.
No matter for me, as .htpasswd solutions don't require a plugin.
Posted 1 year ago #
i'm still on 2.5. not 2.5.1 yet.
Posted 1 year ago #
I already using WP 2.5 when the plugin was installed and works perfectly, but, without any apparent reason, the plugin becomes problem.
Upgrade to 2.5.1 and the problem persist.
Posted 1 year ago #
I've updated WP to 2.5.1 (using the svn method) and AA to 3.6.3 with no improvement. Should we compare PHP and Apache versions? My install's on SuSE Ent 10.1, PHP is 5.2.1 and Apache is 2.2.3.
Posted 1 year ago #
Ok I fixed it.. The problem was occurring I think because the automatic upgrade stuff somehow included the file twice. Theres really no other explanation since it literally was only in the file once. So I added 2 different tests that make sure it doesn't get included twice and the new version works!
Oh ya, and I added an additional security option to password-protect /wp-login.php
Oh ya, and I added an additional security option to password-protect /wp-login.php
Great!
Posted 1 year ago #
aha, well done!
many thanks for working it out
Posted 1 year ago #
ok I just did a fairly large (for me anyway) refactoring of the plugin so much is improved.. Added a couple more security modules that I'm trying to program to be compatible to snort, nessus, and mod_security rules. I'll be working on a submission form for people to contribute their own .htaccess modules.
some changes
* more php4 compatible, no glob, no 2nd parameter for sha1, etc.
* 99.99% accurate test for mod_rewrite capability and .htaccess capability using fsockopen
* started the SID collection to make it easy to add in more security modules
Posted 1 year ago #
I've installed 4.0.2.2 and indeed the install complaint is gone. Good job. ;-)
But now AAPro's options page is broken. I choose the Configuration link from WP's plugins page. AAPro displays links to AAPro and Google 404, then there's the characters "';", then an H2 reading "AskApache Password Protect," and then blank. In FireFox's view source I can see the form tag, then a couple hidden input fields (the last being:
<input type="hidden" name="_wp_http_referer" value="/talk/3l/wp-admin/options-general.php?page=askapache-password-protect.php" />There's nothing more after that. So I'd guess either a malformed concatenation or premature end to some running code.
This topic has been closed to new replies.
