Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 0.7.5

Request #13712 Notify users when a package may maximum_upload_size
Submitted: 2008-04-18 10:19 UTC
From: lsolesen Assigned:
Status: No Feedback Package: PEAR_Frontend_Web (version 0.7.2)
PHP Version: 5.2.5 OS: Win Vista
Roadmaps: (Not assigned)    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 10 + 45 = ?

 
 [2008-04-18 10:19 UTC] lsolesen (Lars Olesen)
Description: ------------ I tried to install a fairly big package (40MB+) with quickinstall from http://localhost/pear/?command=list. However, it fails and no reason or message is given.

Comments

 [2008-04-18 10:51 UTC] lsolesen (Lars Olesen)
It seems that the maximum_upload_size was the problem. However, is it possible to do some kind of validation for the size of the package compared to the allowed upload size, so one can get notified?
 [2008-04-22 12:17 UTC] doconnor (Daniel O'Connor)
(either do this in install documentation / etc; or provide a method of obvious feedback to the user)
 [2008-05-20 21:24 UTC] tias (Tias Guns)
Hello Lars, What did you enter in the quickinstall box, a remote URL like http://... or something local like file://... ? The frontend basically forwards the command to PEAR itself, so I don't really see at what point 'maximum_upload_size' would come in to play, this is for uploading files to a form, righ t? I've seen cases of go-pear (web-installer) silently fail because of a too low memory limit (the installer loads the package in memory). Is it possible that you raised this limit too ?? Greetings, Tias
 [2008-08-02 12:46 UTC] tias (Tias Guns)
No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you.