beernews

Cool stuff, indeed. Thx for the hard work.

I just upgraded. The 8/14 was a reference to the date I first saw a new plugin alert for this.

I didn’t do the full htpass this time as I’ve run into problems with that in prior installs though I was able to hook up some of the other features this time flawlessly. And the interface looks awesome.

Nice work, Apache!

I’m looking for clarity on this issue as well. Modifying the original header would just screw up all of the other pages. The CSS thing won’t work either (different looking pages). Do I really need to create a new header file? And if so, would I need to change:
<?php get_header(); ?> to <?php get_*NEW HEADER FILE NAME*(); ?>
in my new page template?

Create your wp-admin password? Do you mean create your AskApache password? I think after fresh install/upgrade, AAPro user is admin and pass is blank but I could be very wrong.

And to be fair to AA, this has been the only program I could find that RELIABLY protected my images directory which is very important to me. Because he’s one guy though, some of the kinks are still understandably going to be there as his setup is different from mine vs. yours, etc.

I’m just wondering whether there are some kind of instructions on how to clean out AAPro and start again. Someone said once to delete all AAPro lines from WP files but that seems a bit much.

Well, partly resolved. I realized that after activating again, I don’t NEED to set another wp-admin password to still work with the other security options though I love having that extra gate of security.

Deleted my firefox cache and appearance is back to normal.

Maybe deleting the .htpasswda1 file in addition to the htaccess AApro code would have solved the initial password prompt issue?

P.S. I also left a post for the Askapache-search-engine-verify plugin as there was an error there.

No one?

Disabling this did not fix the problem. Something wrong with cache as well. It’s gotta be an Apache Pro/supercache conflict but I’ll take the security plugin over the speed one until I can figure out the issue. ??

Same problem though I used to be able to. My .htaccess reads,

<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine Off
SecFilterScanPOST Off
</Files>
</IfModule>

Maybe taking out async-upload will fix it? Hmm.

i’m still on 2.5. not 2.5.1 yet.

Same activation error here.

Saw that something like this would work…

<Files "wp-cache-phase2.php"
Allow from all
</Files>

If I want to allow multiple files, would this be correct syntax?

<Files "wp-cache-phase2.php,wp-cache-phase1.php,wp-cache-config-sample.php,wp-cache-base.php,searchengine.php,wp-cache-config.php,advanced-cache.php">
Allow from all
</Files>

Not sure if I would need to include directories as well but I imagine so.

I tried your example link and got a warning about snooping around. Does the problem resolve itself if you remove that rewrite rule? I presume there’s a .htaccess in wp-content/ ? Remove that and it might work ok.

Is there a way to block parent directory access for images, etc. and still have supercache work successfully? I created an .htaccess file in wp-content with this code from blogsecurity which, of course, made supercache stop working:

Order Allow,Deny
Deny from all
<Files ~ ".(css|jpe?g|png|gif|js)$">
Allow from all
</Files>

Had to contribute what worked for me.

Otto’s Tips (moderator)

I tried a couple things and then went to #8, the mod security fix. Bingo. Took about 10 mins total to solve the image uploading issue.

Thanks, Otto!!

So sorry, they were caching correctly in my cpanel. I expected to see a bunch of files in the supercache directory as is the case with the wp-cached files in the cache directory.

I didn’t notice a subdirectory underneath the supercache directory. Cpanel’s interface tightly packs things together!

Much thanks, Donncha.

True, yes. I just wanted to confirm that it is actually working because I have seen an indication my wp-admin page that there are super cached files there, seen on the source page for my site that pages are being super cached, and yet I have not yet seen a single file in my supercache directory on cpanel.

Wouldn’t the supercached files appear in the supercache directory if it was actually working? I can confirm though that I am seeing wp-cache files in the cache folder so wp-cache appears to be running just fine.

Much thanks!