Massive errors

  • Resolved axis42

    (@axis42)


    16 years, 11 months ago

    Hi,
    I help a friend of mine with her blog which is at jbwow.com.
    She emailed me today because when she went to her site, all she was a bunch of error codes and thought an upgrade might be needed. I upgraded her from 2.3 to 2.5 but the errors are still there. I have no idea what they mean or how to fix them. Can someone tell me, in relatively non-techy language, what’s going on and how to fix it please?
    Thanks!
    Charles

    the errors are:
    Warning: fopen(/home/.idjie/cmonster/jbwow.com/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: No such file or directory in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 79
    Couldn’t write to: /home/.idjie/cmonster/jbwow.com/wp-content/cache/wp-cache-6666cd76f96956469e7be39d750cc7d9.html
    Warning: flock(): supplied argument is not a valid stream resource in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 88

    Warning: fopen(/home/.idjie/cmonster/jbwow.com/wp-content/cache/wp-cache-6666cd76f96956469e7be39d750cc7d9.meta) [function.fopen]: failed to open stream: No such file or directory in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 223

    Warning: fputs(): supplied argument is not a valid stream resource in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 224

    Warning: fclose(): supplied argument is not a valid stream resource in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 225

    Warning: flock(): supplied argument is not a valid stream resource in /home/.idjie/cmonster/jbwow.com/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 97

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter axis42

    (@axis42)

    Well, no one posted anything here to help solve this but I was able to figure out a solution anyway. In case anyone ever comes across this again, the problem seems to be in the plug in wp-cache which is apparently totally unnecessary tends to break like this a lot and is for some reason loaded in a lot of WP installations by default.

    Anyway, the fix was to use an FTP client and go to the blog’s plugins directory and delete the folder wp-cache. fixed!

    lol.

    wp-cache isnt loaded into any WP installs by default. thats crap, sorry.

    WordPress comes with the plugins — askimet, and hello dolly.

    Thread Starter axis42

    (@axis42)

    It’s loaded into the ones that I’ve installed. Maybe it’s a quirk of the server I use which offers WP as a one-click install.

    Regardless, whooami, you seem to be a snot based on this and other posts I’ve read of yours.
    thanks for coming along and posting useless crap on this thread after it was resolved and soundly ignoring it when I still needed help.

    Hopefully by the time you stop being 13, you’ll have learned some basic decency.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Massive errors’ is closed to new replies.

Tags