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

Bug #11998 Broken emails from user note to bug converter
Submitted: 2007-09-06 15:29 UTC
From: wiesemann Assigned: davidc
Status: Closed Package: pearweb (version 1.16.3)
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.18.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 : 3 + 15 = ?

 
 [2007-09-06 15:29 UTC] wiesemann (Mark Wiesemann)
Description: ------------ The user note to bug converter creates "broken" emails, e.g. like this one: http://pastebin.com/f2bbd7a7 Problems: - almost empty "From:" - escaped quotes (\") - linebreaks broken (\r\n shown) In the bug tracker the text is shown as expected, but no in the emails. It would also be nice to have the note submitter's name and email as the bug reporter, but that might be a more complex task since the bug tracker requires an account and the notes system does not.

Comments

 [2007-11-18 13:33 UTC] dufuz (Helgi Þormar Þorbjörnsson)
It might be doable but if the name is not present or some weird stuff about it we can always just put this in the name "Note Commenter ID 13223432" just to have something ;)
 [2008-01-21 01:59 UTC] davidc (David Coallier)
Actually the person who clicks on "Make this a doc bug" is going to be the reporter of the new bug. Otherwise we'd have to create a new account request, etc etc. This is going to be simpler to manage and implement and I believe is going to be much more reliable and easy to trackdown bugs (Because most people writing comments do not want to follow the status of a bug and keep replying which will make the bugs closed without feedback) Anyways, I have fixed this, committing now.
 [2008-01-21 02:06 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.