Forum Replies Created

Viewing 11 replies - 1 through 11 (of 11 total)
  • Sarah,

    Quick follow up – your code worked perfectly.

    Thanks again,

    Steve

    Wow Sarah,

    “Hope that helps” – h*ll yes, does it ever, and it makes perfect sense. I’ll try it in the morning. And, thanks for your quick reply.

    Thanks again for your useful plugin and for your generous support.

    All the best,

    Steve

    Hi Sarah,

    Perhaps kplusplus was having a similar problem to one I’m having:

    In WordPress versions prior to 3.3.1, the following returned the Page Menu Label:

    $menuName = get_post_meta ($the_page_id, 'menulabel', true);

    Now, since updating to 3.3.1, it returns nil;

    Cheers,

    Steve

    I wonder how many human-hours of time have been wasted clicking that box πŸ™‚

    Hi Craig,

    Did you get anywhere with this? I’ve recently had a similar idea, except I want to take an LSI-grouped keyword list, create a silo category structure and populate it with unpublished empty articles with the keywords as the titles.

    I’m thinking XML-RPC.

    Cheers,

    Steve

    Hi sweyhrich,

    I don’t think its a permissions problem. I think AA Pass Pro gets confused about where its reading and writing things. I end up with artifacts all over.

    I’m not sure if it will help you but I posted a nasty hack that got me going (barely) at topic 196640. That allowed me to protect my Children’s Learning site with others to follow.

    Don’t even try to use the pasword protection — it hasn’t worked since 4.3.5. You can use cpanel to do the same thing without the pain. But the rest of Ask Apache’s work is gold.

    Steve

    Forum: Plugins
    In reply to: Ask Apache Password Protect
    Thread Starter steinitz

    (@steinitz)

    Sorry, the line number is 1836 – don’t change the one at 1363 (it may need changed but I couldn’t see an easy way to do it).

    Also, I had to deactivate then reactivate AA Pass Pro after I made the change. I think.

    Steve

    Forum: Plugins
    In reply to: Ask Apache Password Protect
    Thread Starter steinitz

    (@steinitz)

    Hello,

    I was able to make one minor change to the code and get past the initial check and then do all the protection except password protecting wp_admin. In my case a problem arose because I install wordpress in a ‘main’ subdirectory but put its index.php in root and set these values in settings

    WordPress address (URL) http://example.com/main
    Blog address (URL) http://example.com

    To support that setup I changed line 1547 (give or take) from:

    $home_path = rtrim( get_home_path(), ‘/’ ) . ‘/’;

    to

    $home_path = rtrim( get_home_path(), ‘/’ ) . $path;

    That adds ‘/main/’ to $home_path and fixes it just enough to get me some basic protection.

    Hope that helps somebody,

    Steve

    Hi askapache,

    Thanks for supplying the contact info (wasn’t able to use the webmaster contact form on your site – it gives a not-authorized error). And thanks for continuing to support your great plugin.

    I upgraded to 4.6.1 – it still fails the tests – see below.

    Also, it looks like your fix with the rtrim of ‘/’ is along the right path but the tests still create a wp-content directory in my root directory.

    Let me know what I can do to help with debugging.

    Best regards,

    Steve

    ps. (repeated from another thread) Re mod_auth_digest my host, Hostmonster has stated that they will never enable mod_auth_digest. I explained the issue and escalated it it higher and higher support levels to no avail. Also, I’ve seen some recommendations elsewhere to leave the mod_auth_digest disabled.

    pps. Here is summarized debug output showing just the failed tests (with two exceptions. Note, auth domain looks funny and has to do with the mysterious wp-content directory.

    Array
    (
    [step] => test
    [plugin_data] => Array
    (
    [Name] => AskApache Password Protect
    [Title] => AskApache Password Protect
    [Description] => Advanced Security: Password Protection, Anti-Spam, Anti-Exploits, more to come…
    [Author] => AskApache
    [Version] => 4.6.1
    )

    [scheme] => http
    [host] => example.com
    [root_path] => /main/
    [home_path] => /home/example-server/public_html/example/
    [test_dir] => /home/example-server/public_html/example/wp-content/askapache
    [root_htaccess] => /home/example-server/public_html/example/.htaccess
    [admin_htaccess] => /home/example-server/public_html/example/wp-admin/.htaccess
    [admin_mail] => support@example.com
    [authdomain] => /main/wp-admin/ http://example.com/main/wp-admin/
    [authname] => Protected By AskApache
    [authuserfile] => /home/example-server/public_html/example/.htpasswda3
    [algorithm] => md5
    [key] => $P$BSBJlkDrPS4Tg5mEoyfxQ7YuQ0Ese1.
    [htaccess_support] => 0
    [mod_alias_support] => 0
    [mod_rewrite_support] => 0
    [mod_security_support] => 0
    [mod_auth_digest_support] => 0
    [basic_support] => 0
    [digest_support] => 0
    [crypt_support] => 0
    [sha1_support] => 0
    [md5_support] => 0
    [setup_complete] => 0
    [revision_support] => 0
    [apache_version] =>
    [revisions] => Array
    (
    )
    )

    [pass ] Fsockopen Networking Functionality

    File Permission Tests
    If any of these checks fail this plugin will not work. Both your /.htaccess and /wp-admin/.htaccess files must be writable for this plugin, those are the only 2 files this plugin absolutely must be able to modify. If any of the other checks fail you will need to manually create a folder named askapache in your /wp-content/ folder and make it writable.

    [fail ] /wp-admin/.htaccess file writable
    [pass] /wp-admin/.htaccess file writable

    [ fail] .htaccess files allowed

    Array
    (
    [0] => GET /main/wp-content/askapache/modaliastest HTTP/1.0
    [1] => Host: example.com
    [2] => User-Agent: Mozilla/5.0 (compatible; AskApache_Net/1.0; http://www.askapache.com)
    [3] => Accept: application/xhtml+xml,text/html;q=0.9,*/*;q=0.5
    [4] => Accept-Language: en-us,en;q=0.5
    [5] => Accept-Encoding: none
    [6] => Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    [7] => Referer: http://www.askapache.com
    )

    HTTP Digest Authentication
    Now we know the encryption and apache module capabilities of your site. This test literally logs in to your server using Digest Authenticationts, providing the ultimate answer as to if your server supports this scheme.

    [fail ] Major bummer… you don’t have mod_auth_digest! (included in apache since 1.1)

    [fail ] Basic Authentication Attempt using Crypt Encryption

    Array
    (
    [0] => GET /main/wp-content/askapache/basic_auth_test.gif HTTP/1.0
    [1] => Host: example.com
    [2] => User-Agent: Mozilla/5.0 (compatible; AskApache_Net/1.0; http://www.askapache.com)
    [3] => Accept: application/xhtml+xml,text/html;q=0.9,*/*;q=0.5
    [4] => Accept-Language: en-us,en;q=0.5
    [5] => Accept-Encoding: none
    [6] => Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    [7] => Referer: http://www.askapache.com
    [8] => Authorization: Basic dGVzdE1ENTp0ZXN0TUQ1
    )
    Array
    (
    [0] => HTTP/1.1 404 Not Found
    [1] => Date: Fri, 22 Aug 2008 09:11:34 GMT
    [2] => Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8g DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
    [3] => Accept-Ranges: bytes
    [4] => Content-Length: 78
    [5] => Connection: close
    [6] => Content-Type: text/html
    )
    [fail ] Basic Authentication Attempt using MD5 Encryption

    Array
    (
    [0] => GET /main/wp-content/askapache/basic_auth_test.gif HTTP/1.0
    [1] => Host: example.com
    [2] => User-Agent: Mozilla/5.0 (compatible; AskApache_Net/1.0; http://www.askapache.com)
    [3] => Accept: application/xhtml+xml,text/html;q=0.9,*/*;q=0.5
    [4] => Accept-Language: en-us,en;q=0.5
    [5] => Accept-Encoding: none
    [6] => Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
    [7] => Referer: http://www.askapache.com
    [8] => Authorization: Basic dGVzdFNIQTE6dGVzdFNIQTE=
    )
    Array
    (
    [0] => HTTP/1.1 404 Not Found
    [1] => Date: Fri, 22 Aug 2008 09:11:35 GMT
    [2] => Server: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8g DAV/2 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
    [3] => Accept-Ranges: bytes
    [4] => Content-Length: 78
    [5] => Connection: close
    [6] => Content-Type: text/html
    )
    [fail ] Basic Authentication Attempt using SHA1 Encryption

    [pass ] Basic Authentication Access Scheme Supported

    askapache said

    fixed all the bugs I was notified about

    How do we notify you?

    Thanks,

    Steve

    Forum: Plugins
    In reply to: Ask Apache Password Protect
    Thread Starter steinitz

    (@steinitz)

    Hello,

    AA Pass Pro 2.6 creates a wp_content folder in my site’s root directory. I think my site setup is confusing AA Pass Pro. WordPress is in a subdirectory called ‘main’ but the WordPress index.php is in the site’s root directory.

    Re mod_auth_digest my host, Hostmonster has stated that they will never enable mod_auth_digest. I explained the issue and escalated it it higher and higher support levels. Also, I’ve seen some recommendations elsewhere to leave the mod_auth_digest disabled.

    Ask Apache: is the fact that mod_auth_digest is disabled prevent AA Pass Pro from continuing?

    Man, I’d really like to get this going. I feel naked without it. Is anyone successfully using the new AA Pass Pro on shared hosting?

    Thanks,

    Steve

Viewing 11 replies - 1 through 11 (of 11 total)