Thread Starter
zesty1
(@zesty1)
I take that back, it’s not writing to the new log location at all, the directory is writable and there are no errors saving. it just continues to save to new location (it does however edit the nginx file properly which is also outside of web root)
My question then is why cant WP edit the folder? its owned properly by www:www, permissions are right.
I do notice that if I create the folder myself it wont give an error at all, but it wont write the log files. Id assume for the same reason that if i delete the folder it cannot create the folders on its own.
besides ownership or permissions, what could it be?
Hi. I didn’t notice any warning before updating the Better WP Security plugin (I have it installed on 3 of my 5 websites). As a result I didn’t deactivate Better WP Security and after updating, I lost access to all five websites. After several hours and some help, I was able to get the sites back up. My mistake, I realize, but before I update the plugin on the other two websites, I want to make sure my doing so (after deactivating Better WP Security) will not cause me to lose my websites again. I apologize if this seems like a silly question, but I can’t afford the time it takes to get them back. I love the security you all provide with your plugin, it has worked beautifully, but after yesterday’s scare, I want to make sure I’m not going to do that again. I appreciate any insight you might provide me. Thank you!
Thread Starter
zesty1
(@zesty1)
I also cant close the ‘iThemes Security is almost ready’ box… its always there. i have tried hitting every button and also the ‘x’
Thread Starter
zesty1
(@zesty1)
Clearing PHP-APC cache fixed the notice that wouldnt go away. It still wont’ write to the proper folder though. Ownership and permissions are correct. I find it odd that it wouldnt create the directories when i specify a path however… but it WILL create them if its in /wp-content/uploads.
