After updating our site with the latest Anti-Splog 1.0.6 and Avatars 3.5.2 our entire site fails to load. I've removed all files for both plugins and the site still stops loading all content, it seems, at the point where the first avatar usually displays.
But like I said, ALL files for both plugins have been deleted. Yet all pages still load only the header and stop. Everything was functioning fine prior to the attempted plugin updgrades.
Upon update of either of these plugins, was anything altered in the database that I can fix? I tried reinstalling the previous versions of both, to no avail. Any other suggestions? I'm so glad I was doing this on our test site first!
OK, I just confirmed something went seriously awry when attempting the upgrade to Anti-Splog 1.0.6 from v.1.0.5. If anyone else ends up with a broken site after the update try this:
1. Remove all Anti-Splog files (from plugins and mu-plugins) 2. Drop the table "wp_ust" from from your database. 3. Reinstall v.1.0.5 (Follow instructions bundled with that version!) 4. Confirm wp_ust table has been created, or run the SQL text from v.1.0.5 (In Order!)
This worked for me. Until I did this, the main blog header would load, but nothing else. Hopefully it had nothing to do with Avatars and the timing was just a coincidence. Checking that now...
Responses (3)
Member (joined April 2009) Likes (0)
OK, I just confirmed something went seriously awry when attempting the upgrade to Anti-Splog 1.0.6 from v.1.0.5. If anyone else ends up with a broken site after the update try this:
1. Remove all Anti-Splog files (from plugins and mu-plugins)
2. Drop the table "wp_ust" from from your database.
3. Reinstall v.1.0.5 (Follow instructions bundled with that version!)
4. Confirm wp_ust table has been created, or run the SQL text from v.1.0.5 (In Order!)
This worked for me. Until I did this, the main blog header would load, but nothing else. Hopefully it had nothing to do with Avatars and the timing was just a coincidence. Checking that now...
Lead Developer (joined May 2009) Likes (0)
Very weird. Not sure how that happened, maybe the error was cached?
From the error seems it had to do with an activated antisplog widget.
Member (joined April 2009) Likes (0)
Even more interesting is that I've never activated any Anti-Splog widget.
Weird indeed. Thanks again.
Become a member