Nobody out there having the same problems?
I have seen that Wordfence was able to change my htaccess file.
But thats all….
Caching is still not active.
Some additional info about my blog:
My blog is not installed in my root dir. I have put it into a subfolder e.g. domain.com/blog/
Thanks
I haven’t had this problem.
Are you running any other security or caching plugins?
Your subfolder setup shouldn’t be an issue as long as WordPress is set up correctly in its own General Settings page for paths and URLs.
After you created the wpcache folder and changed the permissions, did your permission settings stay?
Hi sdayman,
There is no other security or caching plugin.
To be sure that no other plugin is disturbing I have disabled them and tried it again. No success!
I think you mean “wfcache” instead of “wpcache”. After creating “wfcache” I changed the permission to 777.
The permission of that folder is still the same. Nothing changed.
Thanks
Edit:
Only one file “test.php” is created inside “wfache”.
Thats all I can see there…
I’ve not tried this for non-scan issues, but enable Wordfence debugging and then enable caching. Maybe the detailed scan window will show the activity that’s deactivating the cache.
Tried this but didn’t see any entry in the detailed scan window.
Isn’t there another log file?
Not that I’m aware of. Bummer.
If all else fails, use Wordfence Options and set it to delete word fence tables and data upon deactivation. Then delete the plugin, clean up .htaccess and reinstall the plugin. Unless someone has a better idea.
Hi,
Something has changed since last update.
After updating WP and Wordfence to the latest available versions, I have tried it again and now the behavior has changed.
After enabling “Falcon Engine” the selected option does not change back to “No performance improvement” anymore.
But that’s all… caching is still not available.
To check if its working, I have enabled debugging mode and debugging comment. I was not able to see any comment below the html tag on any page.
Thanks
Hi @ferhatakguen,
Please try the following:
Scroll to the bottom of the Wordfence options page. Check the box to disable config caching. This will stop Wordfence from using a file to cache it’s own options which are stored in the database. That way we’re sure that any options you set (like enabling falcon) will be saved and you’re not having an issue caused by using a disk cache to store serialized config data for Wordfence.
Save your options once you make that change.
Then go back to the performance setup page and make sure caching is still enabled. Clear the cache. Make sure that option to insert a comment for debugging is still enabled.
Then hit a page you expect to be cached. Then hit browser reload to get the cached version. Check the HTML source and see if it is the cached version.
Also check the wfcache directory and subdirs to see if anything has been written.
If it’s not caching and nothing has been written, check your web server error log if you have access to that and let me know if there are any errors in there. Also let me know that you’re running Apache or LiteSpeed or Nginx or what your web server is.
Thanks!!
Hi,
I did exactly what you said. Still no caching.
The directory wfcache only contains the file “clear.lock”. Nothing else.
I don’t have access to the error.log. But here are some info about the webserver:
– Apache2 (API version 20051115)
– PHP 5.4.26
Do you need any other information?
Thanks,
Ferhat
I think you can request the error logs from your hosting provider. I’d provide them a date and time range along with your domain name so they can search appropriately
tim
Hello tim,
I was able to enable php error logging via htaccess
e.g.
php_flag log_errors on
php_value error_log /www/htdocs/myaccount/mydomain.com/errorlog.txt
I have repeated my steps in wordfence but nothing was logged inside the logfile.
My hoster told me that I can’t access the apache error.log because it’s “shared hosting”.
Thanks,
Ferhat
I knew they would say that, but that seems weird that they wouldn’t be able to provide an output of errors that pertain to your site. Let’s say your domain is called ferhatakguen.com. Presuming you are on Linux hosting and not Windows can you ask them to run this command :
cat error_log | grep ferhatakguen.com >> ferhatakguen_errors.txt
and send you that file?
That should only have things associated with your domain. (also note that the name of their error file may be different as well but I’m sure they know that.
Let me know what they say.
tim
Hello tim,
I wrote them an email couple of minutes ago. I told them they should just filter the errors of my domain. Technically this is possible but I don’t know what kind of internal rules they have…
I will let you know what they’ll say.
Thanks,
Ferhat
Hello tim,
they sent me my error.log. There was nothing relevant inside.
After that I tried several other things.
1) I changed the ownership of my wordpress folder to the user www-data
2) As I told you before my wordpress is installed in a subfolder (/blog). I had created a redirection to that folder using htaccess (located in my root).
RewriteEngine On
RewriteRule ^$ /blog [L]
In wordpress settings I had entered for “Site address” and “wordpress address” the same url e.g. mydomain.com/blog
Now I changed this. I used the method described here.
I changed my wordpress settings to:
site address = mydomain.com
wordpress address = mydomain.com/blog
After that I enabled falcon engine again and opened several pages.
I could see now that wordfence was able to create some subfolders inside “wfcache”.
But the opened pages didn’t contain a wordfence comment.
I recognized that when enabling falcon engine wordfence always changed the htaccess file inside mydomain.com/blog/
Just for testing I copied the wordfence lines of the modified htaccess file and pasted it into the htaccess file of my root.
Now it looks like that it’s working. I can see the wordfence comment line.
So the question is … Why do I need to modify the root htaccess file manually?
Here are my current htaccess files:
in root: http://pastebin.com/PPDDn6iU
in blog: http://pastebin.com/mSafJwTk
Thanks,
Ferhat
