Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0
Bug #9589 Link input field on requestform too short
Submitted: 2006-12-09 00:39 UTC
From: walter Assigned: cellog
Status: Closed Package: pearweb (version 1.0.0RC1)
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.15.0    
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 : 20 + 7 = ?

 
 [2006-12-09 00:39 UTC] walter at php dot net (Walter Hop)
Description: ------------ On http://pear.php.net/account-request-newpackage.php as of 2006-12-09, the input field "Link to browseable online source code" has a maximum length of 5 characters: <input type="text" name="sourcecode" size="40" value="" maxlength="5" /> The logical purpose of this field seems to be entering a URL. In that case, the maxlength should be much longer. Test script: --------------- lynx -dump -source http://pear.php.net/account-request-newpackage.php | grep '"sourcecode"' Expected result: ---------------- <input type="text" name="sourcecode" size="40" value="" maxlength="255" /> Actual result: -------------- <input type="text" name="sourcecode" size="40" value="" maxlength="5" />

Comments

 [2006-12-19 16:20 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.
 [2007-04-27 20:09 UTC] cweiske (Christian Weiske)
Some user told us on IRC he had the same problem.
 [2007-04-28 04:48 UTC] davidc (David Coallier)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.