drtillberg
Forum Replies Created
-
Based on Matt’s comment, tried 6.0.24 again (older version) after renaming WF tables. First try worked but then after a delay gave white screen. Then on second try I made sure to disable auto-update for WF and reduce WF memory setting from 256M to less than 128M, which apparently is all I have for this server at the moment. 12 hours later, site is still up and running with WP 4.5 and WF 6.0.24.
Trying to wrap my head around what could be an incompatibility for a WAMP server. WP and WF interact with the AMP (Apache MySQL PHP) just the same as a LAMP. So that leaves the filesystem. Is this about slashes and backslashes in addresses, is it non-‘nix file permissions, or is there some other compatibility it would be necessary for me to monitor?
When I switch themes to, say Twenty Eleven, the mode of failure when installing Wordfence reverts to crashing the whole website with a white screen.
Apache/Windows/MySQL, PHP 5.6.14, Memory limit 128M. Using Piwik,
Thematic
theme, some other things. The WP debug log still does not record the error event. That log has many unrelated complaints about depricated “called constructor method for WP_Widget” in a Thematicfunctions.php
. Nothing about WF or wordfence. I’ll follow up if I can get anything new re: Apache logs. Thx.6.1.3 has improve mode of failure on WP 4.5. When I try to activate, it generates an HTML read error for the activation page: “The system returned: (104) Connection reset by peer” (outside WP).
The improvement is that the plugin is not actually activated after the error, and the site continues to function. Plugin still does not work, but no longer disables whole WP site.
No success.
Changed names of old wordfence tables, re-added WF –> blank website.
Enabled WP debugging, re-added WF –> blank website with no new log entries.
I’ll look at the WF database entries. As for error logs, not sure but Apache might have exited the child process several times with status 255. I don’t have WP debugging active. Thx.
Actually, 6.0.24 only worked temporarily, maybe as a result of caching, eventually that too resulted in white screen. I have deleted the plugin to make site work again.