mlmoore

So far the firewall has remained on – glad to hear the 640 change is due to WF. My SSL caching is still working so far, so I will mark this as resolved.

Thanks for your help Cory!

Well, my host looked into this and found that the wflogs/config.php was owned by the root, and not the user so they updated it.

The file permissions they said should be 755/644 for directories/files. They updated the config.php file and others with correct permissions and user.

I logged in and I was not getting the firewall error and backupbuddy is able to access the wflogs directory. So that was all working great until today, however, I notice the file permissions for config.php are back to 640 – so they have changed “on their own”.

Today I also noticed my SSL caching (basic caching) had been turned off. I turned it back on. Leave for lunch, come back, and now it’s turned back off. I’m contacting my host to see if they think a cron job may be affecting this- I’m not sure what else would be telling my SSL caching to stop. I may need to start a new thread on this.

Thanks for your help on this.

Hmm – I’m finding the
wp-content/wflogs are 755 and the config.php file is 0640.
I’m not sure what I should change them too.

Hi petkovsc,

I’m currently on this. I ran into issues yesterday with my backupbuddy plugin – it’s now unable to do it’s weekly complete backup due to the same reason (same file) that wordfence is having issues with:

Zip warning: could not open for reading: wp-content/wflogs/config.php

I’ll chat with my host on updating the permissions and see what we come up with.

OK – more detailed explanation seems to be needed. First off, I told our host to do the mod_cloudflare – I would have no clue. My “webguy” set up most of cloudflare too.

We “just” moved our sites to a new host and are split in 50 different directions. We’ve never had a webhost manager or cpanel access (our previous host was in the dark ages), and both of these cover so much it’s easy to get lost.

Once I have a chance to figure out where my file permissions are located, I will do so.

Hmm – That’s a bit of a project for me being more a novice when it comes to wordpress. I was hoping this was a known issue or there is a fix for this?

Thanks petkovsc – I ‘ve subscribed to the other thread

I have the same issue once wordfence updated to version 6.1.10 yesterday. Firewall won’t run.

Firewall Error: We were unable to write to ~/wp-content/wflogs/ which the WAF uses for storage. Please update permissions on the parent directory so the web server can write to it.

Thanks
Michelle

Thanks tiagonoronha!

I’ve also been trying to find if Boutique (woothemes) is also compatible but can’t find any info. I’m not sure if it matters if it’s a child theme or not if Storefront is compatible now, but I wanted to make sure Boutique is “ok” before moving to Woocommerce 2.4.0.
Do you know?

Thanks a bunch!

Oh – I’m also using the Boutique child theme with Storefront – is this also compatible with woocommerce 2.4.0??

Thanks again!

Awesome – that did it!
Thank you JamesKoster

My Theme versions are:
Storefront version 1.4.6
Boutique child theme v 1.1.2

Thanks again!

Hi – I’d also like to put my vote in to have the floating bar on my homepage too. I’ve just installed Digg Digg on Thesis, seems to work just fine, except I can’t add it to my homepage.