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

Bug #10133 foreach() error when closing PEAR bug
Submitted: 2007-02-20 09:45 UTC Modified: 2007-02-20 23:10 UTC
From: ashnazg at php dot net Assigned: cellog
Status: Closed Package: pearweb (version 1.5.1)
PHP Version: 5.2.1 OS: WinXP Pro
Roadmaps: (Not assigned)    
Subscription  


 [2007-02-20 09:45 UTC] ashnazg at php dot net (Chuck Burgess)
Description: ------------ I got this error twice this morning, when trying to close two PEAR bugs (9151, 9915) on PhpDocumentor: Warning: Invalid argument supplied for foreach() in /usr/local/web/pear.php.net/public_html/bugs/bug.php on line 397 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/web/pear.php.net/public_html/bugs/bug.php:397) in /usr/local/web/pear.php.net/include/pear-format-html.php on line 705 I have no idea if I've selected (under duress) the correct PHP/Package versions above, because this instance of pearweb isn't on my local system, i.e. I don't know what versions of what you're running pearweb on. I was using Firefox 3 Alpha 2 ("Gran Paradiso") on WinXP Pro, if that proves relevant. Expected result: ---------------- A "closed successfully" webpage message or else a jump back to the bug list webpage. Actual result: -------------- A plain white page containing nothing but the error text: Warning: Invalid argument supplied for foreach() in /usr/local/web/pear.php.net/public_html/bugs/bug.php on line 397 Warning: Cannot modify header information - headers already sent by (output started at /usr/local/web/pear.php.net/public_html/bugs/bug.php:397) in /usr/local/web/pear.php.net/include/pear-format-html.php on line 705

Comments

 [2007-02-20 23:10 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.