Re: [pear-webmaster] Cannot file new bugs, website bug?
[email protected] ("Daniel O'Connor") Thu, 22 Dec 2011 16:04:15 +1030
| Newsgroups | php.pear.webmaster |
|---|---|
| Message-ID | <CAJsZyFBhmuO4-zU=NySo9OP_Ferca9KiY7jm8z0E=7Hh-xmmMg@mail.gmail.com> |
On Thu, Dec 22, 2011 at 3:25 PM, Nick Fenwick <[email protected]> wrote: > Hi there, > > I'm trying to file a bug against Mail_IMAPv2. > > https://pear.php.net/bugs/**report.php?package=Mail_** > IMAPv2&action=Report+Bug<https://pear.php.net/bugs/report.php?package=Mail_IMAPv2&action=Report+Bug>< > https://pear.php.net/bugs/**report.php?package=Mail_** > IMAPv2&action=Report+Bug<https://pear.php.net/bugs/report.php?package=Mail_IMAPv2&action=Report+Bug>> > gives me a header, but a mostly empty page. > > https://pear.php.net/bugs/**report.php?package=pearweb<https://pear.php.net/bugs/report.php?package=pearweb>does the same, when I click to report a website bug. > > I get this behaviour in both Firefox and chrome, on Fedora 15. From the > look of View Source, the page simply cuts off, so I presume you have server > side bugs. > > Here's the last few lines of the webpage source: > > """"" > <!-- BEGIN BUG NAV --> > > <table width="100%" border="0"><tr><td> > <a href="/package/pearweb">**Package home</a> | <a > href="/bugs/report.php?**package=pearweb">Report new > bug</a> | <a href="/bugs/search.php?**package_name[]=pearweb">New > search</a> | <a href="/bugs/roadmap.php?**package=pearweb">Development > Roadmap</a> > </td> > <td style="text-align: right;"> > Status: <a href="/bugs/search.php?cmd=**display&package_name[]=** > pearweb&status=Open">Open<**/a> | <a > href="/bugs/search.php?cmd=**display&package_name[]=** > pearweb&status=Feedback">**Feedback</a> | <a > href="/bugs/search.php?cmd=**display&package_name[]=** > pearweb&status=All">All</**a> | <a > href="/bugs/search.php?cmd=**display&package_name[]=**pearweb&status=CRSLR" > title="Closed bugs since last release">Closed Since Version 1.25.0</a> > </td></tr></table> > <hr /> > > <!-- END BUG NAV --> > """"" > > Potentially a proxy issue or something else between pear.php.net and your browser? Works happily for me