Digitsoft
Forum Replies Created
-
I finally have the answer – had to increase the memory for this WP install (had to bump max mem in php.ini first) in wp-config:
define(‘WP_MEMORY_LIMIT’, ‘512M’);
define(‘WP_MAX_MEMORY_LIMIT’, ‘512M’);The default WP max of 256M wasn’t even enough.
Without setting both parameters I couldn’t deactivate or even reactivate (after physically deleting the WF folder and then unzipping it again).
Here are the WF table record counts:
wfFileMods 4k
wfHits 1k
wfLeechers 58k
wfNet404s 16k
wfScanners 31k
wfStatus 40kSo all along it was a simple memory issue and this alone prevented WF from running the install/upgrade routines fully.
LMK if you want me to try or test anything else…
Nothing obvious in the logs, but I just set up a new VMWare instance to test this without affecting the live site.
I’ll post if/when I find anything concrete.
Couldn’t deactivate WF, so deleted folder
Deleted 2 entries from options table & left other tables
Installed WF and activated, but fields not added
Deleted options data again and all wf tables
Tried to activate, but said “Fatal Error”
– wfHits table created, but has wrong fields shown below
Deleted options data again and all wf tables
Tried to delete the plugin from within admin, but just redirected to site 404
Deleted plugin via shell
Still can’t get it to activate
Added debug line to wp-config, but nothing obvious
Reverted back to working siteIf I get some time later I’ll dig further…
I’m going to restore a backup of the site and see if I can find an answer.
Forum: Plugins
In reply to: [Offers for WooCommerce] Fatal error on Woocommerce updateWorks so far…thanks!
I’ll post if I find anything.
Forum: Plugins
In reply to: [Offers for WooCommerce] Fatal error on Woocommerce updateCool…just got the same thing.
Very nice plugin BTW!
I was able to get a re-install to work – it let me deactivate it this time, deleted the plugin through the admin, deleted the tables from the db, and removed the version number from the options table.
I still have no idea why it didn’t create the 4-6 fields before, but have to assume it’s an upgrade thing.
I’ll dig more when I have time to see if I can pinpoint it…
I didn’t dig far enough I guess 😉
Install goes through without issue and the user has full rights.
Any other ideas?
I’ll keep digging around and see if I can come up with an answer.
Thanks again for WF!
I dug around more and wfSchema has this for table creation, so looks like the code isn’t creating the proper fields.
"wfHits" => "( id int UNSIGNED auto_increment PRIMARY KEY, ctime DOUBLE(17,6) UNSIGNED NOT NULL, IP int UNSIGNED NOT NULL, jsRun tinyint default 0, statusCode int NOT NULL default 200, isGoogle tinyint NOT NULL, userID int UNSIGNED NOT NULL, newVisit tinyint UNSIGNED NOT NULL, URL text, referer text, UA text, KEY k1(ctime), KEY k2(IP, ctime) ) default charset=latin1"I have the same issue – WF 6.1.8
I couldn’t deactivate WF, so just deleted the folder, tables, and anything I could find in the options table. I then reinstalled and reactivated WF, but my brand new wfHits table looks like below and doesn’t look like above:
—
— Table structure for tablewp_wfHits
—CREATE TABLE IF NOT EXISTS
wp_wfHits(
idint(10) unsigned NOT NULL AUTO_INCREMENT,
ctimedouble(17,6) unsigned NOT NULL,
IPint(10) unsigned NOT NULL,
jsRuntinyint(4) DEFAULT ‘0’,
statusCodeint(11) NOT NULL DEFAULT ‘200’,
isGoogletinyint(4) NOT NULL,
userIDint(10) unsigned NOT NULL,
newVisittinyint(3) unsigned NOT NULL,
URLtext,
referertext,
UAtext,
PRIMARY KEY (id),
KEYk1(ctime),
KEYk2(IP,ctime)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;I have htaccess configured to only allow a POST from my home ip or 127.0.0.1 on almost all sites due to attacks.
The POST commands are coming from wordfenceClass.php line 1004 and are POSTing with the server ip and not localhost. I’d have to imagine this is the cause.
When using CURL you can specify the ip with CURLOPT_INTERFACE, but after looking through the CODEX for the function it doesn’t appear it’s available.
Anyway…hopefully there’s a way to POST using localhost because I know I’m not alone in refusing a POST from anything other than localhost.
There should also be a little code added that prevents this looping call from taking down a server.
LMK if there’s anything else I can help with…
Rob
Before I saw your post I deactivated the plugin and reactivated it and the sync problem stopped (at least for now).
I saw the calls in the apache log and the originating IP is my server’s IP.
There were approximately 45,000 hits before I deactivated the plugin.
I emailed the first 350 log lines to you just now.
I’ll dig into it further to see if there’s anything I can find.
Forum: Plugins
In reply to: [Auto Featured Image from Title] Bug Found & FixedI just tested the new version and all is working fine – even after removing the settings from the db.
Glad to help…