RE: [PHP-QA] Modifications to bug system

> > Also, I have been thinking that perhaps it would be advantageous to > > incorporate a bug reporting utility directly into the PHP interpreter. > > Perhaps it could kick up whenever certain types of errors (like core > > errors) were encountered. Another thought is that the user could call a > > function and a bug reporting utility would be generated on the page. > > > I am sure that we would get more false bug reports this way, but the > > advantage would be that we could automatically generate accurate > > platform and version data. > > PHP could generate a clickable link which automatically points to bug > report form, include build data, Os data and module data. > > <A > > HREF="http://bugs.php.net/autoreport.php?build=20000803&os=win2000 > &modules=wddx%20bcmath">Please > click this link to report a bug</A> > But I´m not sure how to implement this and how to catch important > errors, a link like that on every error and every user will be invited > to spam our database... > > The better solution: > We could ship an automatically generated .html file with every php > binary distribution which includes data like OS and version, tarballs > could include a general form with OS selection. I think this is a good solution. I recently submitted a bug report (core fault) that seemed pretty random at first. Basic info like OS/Config/ect. wouldn't have helped a bit in this case. If it had been an automated process it probably would've become just another lacking-report. I like the last solution. We could generate a .html file when PHP was installed for instance, that would fill in general info like OS, version, ect. to make it easier to submit a quality report. I agree with having the users register before submitting a report. Like was previously said, an extra minute or two is peanuts if you can't get your application/script to work. jason _______________________________________________________ Site Design, Hosting, and E-Commerce at www.webpipe.net