Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • Forum: Fixing WordPress
    In reply to: Blog has vanished
    Thread Starter danielmcneese

    (@danielmcneese)

    If I tried to open a link to it in a new window, it would try to load for a while and then give a “not found” error. If I tried to open it in the same window it would pretty much ignore me; I’d get a brief indication of loading, but the same page would remain open.

    I speak in the past tense because I tried a reboot and it worked; I can access my blog again.

    Sigh. Thanks for your time, ladies and gentlemen. This “WTF was that all about” moment has been brought to you by Dungeon Games.

    Resolved.

    Forum: Fixing WordPress
    In reply to: Blog has vanished
    Thread Starter danielmcneese

    (@danielmcneese)

    I just tested it on someone else’s computer, and you’re right. It came up fine for them. But it’s still not working for me.

    This is very odd… I can access the rest of the internet – even the rest of my own site – just fine, but not my own blog on my own computer? While everyone else can?

    Thread Starter danielmcneese

    (@danielmcneese)

    There are files in the wp-content/cache/ folder. I don’t know what’s writing them, as I’ve had the wp-cache plugin turned off since before the folder was created.

    There’s one file in it called “wp_cache_mutex.lock,” and the size of it is given as 0. For the rest, there are over a dozen pairs of files like this:

    wp-cache-0607708726832460ffd4c825cb89de68.html
    wp-cache-0607708726832460ffd4c825cb89de68.meta

    Each pair starts with “wp-cache-” and ends with “.html” for one and “.meta” for the other, but has a unique string of numbers and letters in between.

    Since the blog started working again I’ve posted one comment and published one draft. Anything else I should tell you?

    Thread Starter danielmcneese

    (@danielmcneese)

    kmessinger: Wait, are you saying that what I just did should not have worked?

    Thread Starter danielmcneese

    (@danielmcneese)

    I just cracked open my FTP program to take a look, and now that you mention it there was no /wp-content/cache/ folder. Which was apparently the problem, since I just created one and suddenly everything is working again. I have no idea what happened to the old one, but I’m quite sure I didn’t go in and delete it myself.

    Thanks for the help. I’m marking this as resolved.

    Thread Starter danielmcneese

    (@danielmcneese)

    Actually, it was already inactive. I just turned it on to test it, and got the same result (it’s back off now).

    Thread Starter danielmcneese

    (@danielmcneese)

    Jeremy,

    After further tinkering I’ve discovered that your suggestion partially works. I can’t get the permalinks to work the way I had them before (which was date-and-name-based), but leaving it in default mode fixes the problem.

    I’m not exactly happy with this, but the blog is still small enough and little-known enough that I should be able to clean up any mess this causes manually. So I’m going to do it that way and mark this one as resolved. Thanks again for your help.

    Thread Starter danielmcneese

    (@danielmcneese)

    Is there more information I can provide that might help?

    Thread Starter danielmcneese

    (@danielmcneese)

    Thanks, but I had no success with this. If it matters, I have the “Customizable Permalinks” plug-in on (a warning message popped up mentioning it).

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