• I get the following error when I attempt to upload a large jpeg (~2Mb). I don’t get errors and everything works fine with smaller images. (And yes, I have the Options-Misc-Max_Size set to 4096KB. (Note that after the warnings, it claims the upload was a success, even though no upload takes place.) Any help appreciated!:
    Warning: Unable to open ‘none’ for reading: No such file or directory in /home/httpd/html/bunny/wp-admin/upload.php on line 171
    Warning: chmod failed: No such file or directory in /home/httpd/html/bunny/wp-admin/upload.php on line 177
    File uploaded!
    Your file 2004–07–06 005.jpg was uploaded successfully!
    Herea€?s the code to display it:
    <img src=”https://XXXXXXXX/bunny/wp-content/2004–07–06 005.jpg” alt=”Bunny lounges under a chair.” />
    Image Details:
    Name: 2004–07–06 005.jpg
    Size:0 KB
    Type:image/pjpeg

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter Anonymous

    BTW the subject was supposed to read: “Unable to open ‘none’ for reading” error w/ large images only.

    Do other smaller images upload okay ?
    It could be a problem with the /tmp dir on the server.
    Images are actually uploaded to /tmp first, then when it is in completely, the system copies it to your actual upload dir and deletes the /tmp one.
    You could contact the host just to check if there is a problem, and if you have full access to all your root directories (html / mail and various others) search around.
    It may also be useful to experiment with files to see at what size this occurs – try it in 500KB increments initially.
    I don’t think this is a wp issue though, more of a hosting one.

    Thread Starter Anonymous

    Smaller images work fine.
    Space isn’t a problem. (It’s my linux box, btw. So if there’s something to try as root I’m all ears.)
    Any other ideas? Googling on the error shows other people (not WP-specific) with the same issues in upload.php. They’re also able to upload text files and small images, but upload.php seems to puke for others on 2M files as well.
    Do you have upload enabled? If so, maybe you could up your size allowed to 4M and upload a big picture? It *seems* like upload.php is broken, but it also seems like more than a handful of people should have attempted to upload 2M+ images and noticed the problem.

    I don’t know enough about things like this, but is there a setting somewhere that governs the /tmp dir and the space it is allowed to use ?

    Thread Starter Anonymous

    I’d really like to know if anyone else can replicate this “bug.” It’s damned annoying. I just want to post images out of my camera at the default, hi-res setting… Surely other people store 2M images.

    I just tried to upload a 2.05MB file.
    I get the same error as yourself.
    Speaking for myself, I wouldn’t upload such a large file for 2 reasons:
    1 – People wanting to view it would have to wait ages for it
    2 – My bandwidth would be used sooooo quickly.
    I’d suggest an email to your host asking for advice on loading such large files using a php uploading script and not ftp – which is of course an option still.

    Thread Starter Anonymous

    Like I said before, it’s my machine. I am my own host. Hence my posting here. As to why I’d want 2M files, I expected that the thumbnail option would do something. (I can’t figure out what it does, yet.) All of my images in my web gallery, in my stored directories, and so on, are all about 2M raw. I don’t want to have to create thumbnails by hand when software is capable (or should be capable) of resizing it on the fly or as needed.
    So, neither bandwidth, or people waiting for ages should be a problem if
    a) I could understand this stupid error! and
    b) I could figure out what the thumbnail option in WordPress upload does, and how to use it.
    Anyone? Buhler?
    (Thanks for confirming it’s not just me, by the way. Obviously, there doesn’t seem to be a point in allowing WP users to customize the maximum allowable uploads if upload.php pukes on them. I don’t see this documented anywhere.)

    It seems that is a server side configuration problem . If you can change MAX_FILE_SIZE and MAX_POST_SIZE in the server, the problem may be fixed. (sorry for my english ?? )
    Greetz.

    Thread Starter Anonymous

    did anyone resolve this? I am having the same problem

    timinfosentialcom

    (@timinfosentialcom)

    I had an identical problem – setting upload_max_filesize in php.ini to 10M resolved it.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘“Unable to open ‘none’ for reading” error w/ l’ is closed to new replies.