Not signed in (Sign In)

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

General Support: PHP memory limits - impact on file size

Bottom of Page

1 to 4 of 4

  1.  
    • CommentAuthorliberta
    • CommentTimeMay 15th 2006
     
    My host enforces memory_limit = 12M.

    I can upload pictures over 1Mb but it crashes the program.

    1)plog-upload.php fails mid way through reloading page so all I get to see is a blank page
    2) I can navigate to existing albums and see them
    3) When I navigate to album that has large file in it, I get white screen.
    4) Worse when I navigate to the collection, I get a white screen, so unless I know how to use my history bar I am completely lost.

    I have checked the sql tables and the directories. The files are successfully uploaded, and record stored in tables. No thumbs file is created.

    Fortunately I have a friend online with another host - who does not enforce a memory_limit at all. We tested the self same files uploaded and of course he gets no problem.

    I searched the discussion forum and found that someone previously had similar problem and made similar suggestion.
    http://www.plogger.org/forum/comments.php?DiscussionID=320&page=1#Item_0

    They suggested that Plogger make it clear in documentation that a large memory_limit or none at all is required for this software. I second that.

    I also suggest that Plogger be amended to handle such failures gracefully. You need to test for file size on upload and give a helpful message if it is going to cause a problem. And then test for file size on display and give a helpful error message. White screens are not very user friendly!!
    •  
      CommentAuthormike
    • CommentTimeMay 16th 2006 edited
     
    This is why we are having a public "Beta Test". Since I have never personally encountered a white screen in my tests on various servers, error handling was not provisioned for in this particular scenario. We release a beta version in the wild so it can be tested on the 13 million different server configurations. Apparently it works better on some than others.

    Here is a question for you, how does a server-side script determine the size of a file before it is uploaded? To do this with regular scripting, you'd have to gain access to the client file system, which is off-limits to Web pages. See the problem? I guess we could display your server's upload limit and memory limits on the upload page, but following those guidelines is still up to you.

    Plogger is still pretty young in it's development, and we appreciate your feedback. Furthurmore, Plogger makes no claims that is works on all possible server configurations. While we strive for 100% compatibility, we acknowledge the fact that this goal is probably impossible to attain.
    • CommentAuthortimpadden
    • CommentTimeSep 9th 2006
     
    I had the same problem uploading files. I sent them to the upload folder then went to import them and got a white screen. I am not very computer savvy so it stopped me in my tracks. If size is the problem then I have a real problem . 90% of my photos are 5 MG or better and resizing all of them is not really an option.
    • CommentAuthorddejong
    • CommentTimeSep 9th 2006
     
    There's no real way to recover from hitting the PHP memory limit. There is no error or exception triggered. You could check the filesize before generating the thumb ... but you would have to guess how much memory it will take uncompressed, how much additional you need for Plogger itself and temporary objects, and make an educated guess as to whether the generation will succeed.

    Working with images you will always need memory -- it's certainly not the fault of Plogger; it can only handle files as large as the memory space you give it allows. One of the benefits of doing it through AJAX would be that each request can succeed or fail without brining down the whole ship, as it were. If one thumbnail dies, the user can be alerted separately, without the page itself dying.

    However, there are freeware batch (read: many at once) image resizing utilities for every conceivable OS. I'd be happy to suggest some for your OS (XP, OSX, Linux). Presizing it always an option ... easier on the bandwidth and storage space, and easier on your users that want a reasonable full image (there are a select few people that want or need a full 7.1 MP original).

    If you keep refreshing the import script, it has been known to eventually complete and display a success message. The reason ... a few thumbnails are generated and added, and the script dies. Do it again, a few more. Keep doing that, and shortly thereafter all the files have thumbnails and the script succeeds, not killed off by the max memory or execution time.

    Best of luck,
    Derek

1 to 4 of 4

  1.