Cache Nightmare Right now.. Fixed

by Penny on 10/12/08 at 1:47 pm | 45 views

Cache Nightmare Right now.. Fixed

Two of my fave plugins have caused an absolute nightmare to my servers today.. sorry for anyone who visited :(

BackupWordpress, was going over-board and backing up multiple times a day (not even an option in the settings) and doing all my blogs and sites, subdomains, etc.. basically getting carried away.

Bluehost Suspended my sites, when I called - they said that my backup files were taking up 160GB (yes.. GB) of space.. Oh My God.

7 Hours later, Im still in the process of deleting.. but this site (wordpress) didnt come back online until Wp Super Cache was removed.. but by removing it (as per instructions).. I can now login to the backend and can visit the homepage, but 20 mins ago found out from someone that no matter which post you click on.. you get a 404 error to my main site (pennybutler.com).

It’s 1am now..  I have to go to bed to get up for work in the morning.. I can’t find the problem.. there are no cache files left, the .htaccess is as empty as I can make it.. Im sorry if you are trying to access any of the themes or plugins in the meantime.. I can’t fix it til tomorrow night.. :(

=== The Solution ===

Solution ended up being really really easy. I went to work and discussed with the programmers, and through them asking questions I worked out that it was probably the permalinks.. and YAY that worked.. a 1 minute fix..

 Settings -> Permalinks

Changed it back to Default

Permalinks Default

 Clicked SAVE

Then turned my custom Permalinks back on.

Permalinks Custom

SAVE. SOLVED. BRILLIANT.

 

 

Liked this article? Read another similar article.

If you enjoyed this post, make sure you subscribe to my RSS feed!

One Response to “Cache Nightmare Right now.. Fixed”

  1. David (1 comments)

    Feb 7th, 2009

    Isn’t it crazy how the wierdest things can happen in wordpress and you try all sorts of things to fix the problem and then it always (most often) turns out to be something as simple as how you fixed the problem you talk about in this post………… I recently upgraded to Wordpress 2.7 on my blog as well in the root directory and I did it manually………. not long after I started getting 500 Internal Server errors and I couldn’t figure out why….. my webhost figured out that my file and I’m assuming directory permissions weren’t correct and they set the permissions for me and so far I haven’t had another problem (Thank God). I know that was a big sigh of relief for you when you got this fixed.

    David’s last blog post..Men’s Crocheted Board Cap In Burnt Pumpkin Solid

Leave a Reply



Fatal error: Call to undefined function get_commentwitter_input() in /home/pennyb/public_html/wordpress/wp-content/themes/gothamnews/comments.php on line 76