Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • I got my site back up and working!

    I went through all the above forums/threads and none of them applied to me. I tried them, just didn’t solve my issue.

    I’ve semi-documented my issue on my own site here

    Chiefly, I think it’s down to creating a new user for your MySQL database.

    One thing that puzzles me saeed, how did you manage to upgrade your 2.3.3 to 2.5 with Fantastico? I could not do that, and had to delete my existing wordpress installation.

    Has this been solved yet?

    I also looked at those links and the solution was for a “dashboard” problem. Not quite the same as the “widgets” one.

    I had the same problem – except I didn’t upgrade. I was on 2.3.3, then all of a sudden, 20 hours ago, it just konked out and I got the same error log from widgets.php line 315.

    So then I tried upgrading files to 2.5.1 but that didn’t change much. Still no access to the webpage. Then my error_log file got too big (45 megs) so I couldn’t check the error anymore.

    Unfortunate part is, it just happened with no changes from myself. Analytics showed people accessed my site around 04:00 (GMT) then at 06:00 (GMT) when I woke up and went to update blog, I got a blank page.

    Any help would be much appreciated, I’m in process of uploading an old backup – see how that goes.

    I just recently tried using “private posts” that are available to a specific subset of members. Not just “all” logged in users.

    We want our actual paying members to be able to view private posts, but general internet users/subscribers not. I use “Role Manager” plugin to choose the members and their ability to read private posts.

    Not using “password protected posts”

    My solution would be to have super-cache enabled, but wp-cache disabled for logged in users, just like russellgreenwood.

    All I’ve done is reduce the “expiry time” from 3600 default to 1 second. 0 seconds didn’t work. Hopefully, this doesn’t increase the load on the server too much.

Viewing 3 replies - 1 through 3 (of 3 total)