Forum Replies Created
-
Posts
-
Agreed.
I got around the problem, for now, by patching the File_Logger.php’s “find the directory to write to” method and statically point it to a folder that I DO have write access to. This let me disable the logging. However, when I tried to reset the file back to its original, it seems the setting doesn’t “stick” and the file resumes erroring.
So, I guess now we’re running with a “custom” version of this plugin.
As a paying user of this plugin.. this, IMO, is ridiculous. I’m not a PHP developer. I shouldn’t have to write code to solve problems that this plugin introduces.
I wanted to add to this. Frankly, this answer is a hogwash, washing hands type of response.
It’s VERY COMMON (I’d dare say the norm) to NOT have write/create access to /tmp as a non-root user. The page where you show this information, is the same as the page where you enable/disable the functionality. Given this, it seems like there should be a way to recover from this.
I now have this same issue. My hosting company, WPEngine, has stated that they don’t allow /tmp writing. They have suggested that we get help from the plugin author.
And, basically, both of you are pointing the finger at each other. Blah.
We have tried every permutation to fix this. Turning on and turning off the plugin. Looking through the database for a field or setting to switch. So far, we’ve not found anything to fix this problem.
I have lost 8+ hours of work from this. I can’t recover that time. Thankfully, I have a backup from that point in time.
I’m VERY frustrated by this. When YOUR product isn’t working well for ajax queries, and I turn on YOUR logging, I lose 8+ hours of work. And you wash your hands.
