• Resolved nobodywho

    (@nobodywho)


    hi all, i did went around the forum to find if this topic was resolved somewhere else but couldnt find the answer i need.
    on a similar topic it has been suggested to get in with a ftp and change the commands creating the error, but i am not a code-savvy person, i got no idea what to do.
    i downloaded on my notepad2 the file that starts all of the errors, i located the line which seemingly starts it all but dont know what to do with it.
    if i got it right is this one:
    $mutex = fopen($cache_path . $mutex_filename, ‘w’);

    inserted in the command:
    }

    if ($use_flock)
    $mutex = fopen($cache_path . $mutex_filename, ‘w’);
    else
    $mutex = sem_get($sem_id, 1, 0644 | IPC_CREAT, 1);
    }

    please help?

    below is the message i get instead of my blog:

    Warning: fopen(/home/.greystoke/no_body/weedyconnection.com/blog/wp-content/cache/wp_cache_mutex.lock) [function.fopen]: failed to open stream: No such file or directory in /home/.greystoke/no_body/weedyconnection.com/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 79
    Couldn’t write to: /home/.greystoke/no_body/weedyconnection.com/blog/wp-content/cache/wp-cache-03e6c71fcba1755e3d0b6d358361d1bd.html
    Warning: flock() expects parameter 1 to be resource, boolean given in /home/.greystoke/no_body/weedyconnection.com/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 88

    Warning: fopen(/home/.greystoke/no_body/weedyconnection.com/blog/wp-content/cache/wp-cache-03e6c71fcba1755e3d0b6d358361d1bd.meta) [function.fopen]: failed to open stream: No such file or directory in /home/.greystoke/no_body/weedyconnection.com/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 223

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

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

    Warning: flock() expects parameter 1 to be resource, boolean given in /home/.greystoke/no_body/weedyconnection.com/blog/wp-content/plugins/wp-cache/wp-cache-phase2.php on line 97

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter nobodywho

    (@nobodywho)

    and now all is saying is:
    Couldn’t write to: /weedyconnection.com/blog/wp-content/cache/wp-cache-a19e23b1b57a79482dbf5c2c7dae35d3.html
    ?

    Thread Starter nobodywho

    (@nobodywho)

    i would like to start with an aknowledgment of appreciation.
    i spent the past two days on this forum, looking at people responses and following detailed pathways to errors solutions.
    i fully understand that the times donated by so many of you guys is priceless, together with unlimited.
    by blog collapsed two days ago, as you can read up there.
    since then me and another friend blogger of mine with a better knowledge of coding tried different avenues:
    -we upgraded my blog to the newest version (2.51, even thou the dashboard says it is only 2.5)
    -we tried to change the theme in case was an issue theme-related
    – i followed throu the instructions of the threads: http://wordpress.org/support/topic/153689
    changing permissions;
    http://wordpress.org/support/topic/136054
    trying to cahnge permissions in various files even if i dont have the files they talk of in this thread;
    i even had a good look thru-out whole of my files for indications of hackers like this thread:
    http://wordpress.org/support/topic/168964
    and this:
    http://wordpressphilippines.org/blog/has-your-wordpress-been-hacked-recently/
    but couldnt find any telling signs.
    now i’m left with waiting for some light from any of you guys, failing so i might just have to
    1. backup everything
    2. uninstall blog (ie the wordpress software, but not my mysql database_)
    3. create a new wordpress installation, using my existing database to fill it up.
    4. cross my fingers

    any light?
    anyone out there with a torch?

    ok. i had the same problem on my blog, more or less the same error line such as your:

    Couldn’t write to: /blog/wp-content/cache/wp-cache-03e6c71fcba1755e3d0b6d358361d1bd.html

    well, like you, i didnt know what to do, and i farted around for ages on the forums trying to find someone with the same issue and how they fixed it. nothing.

    then i actually read the error message to try make sense of it:

    “couldn’t write to”

    ok, why not? well, i ftp’d to that location and lo and behold, in blog/wp-content/ THERE WAS NO SUCH FOLDER CALLED “cache”. so, how could wp write to /cache/ if it didn’t exist?

    so i created a new folder in that location called cache, gave it a CHMOD of 777 and whacko, problem solved.

    as to WHY that folder wasn’t there, I got no idea. Why should this problem have arisen in the first place? Any smart ideas?

    cheerio

    Thread Starter nobodywho

    (@nobodywho)

    i am so impressed, thanks lu.
    lateral thinking hey?

    how do I open this program? I’m stuck here. 3. Visit the plugins tab and activate the Caffeinated Content Plugin. Where are the plugins?

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

The topic ‘[function.fopen]: failed to open stream’ is closed to new replies.