Bug #7947 [Fbk]: Bugtracker asks for password that doesn't exist

Edit report at http://pear.php.net/bugs/bug.php?id=7947&edit=1 ID: 7947 Updated by: pajoye@php.net Reported By: wiesemann at php dot net Status: Feedback Id: 7947 Type: Bug Package: Bug System Operating System: Irrelevant PHP Version: Irrelevant Assigned To: pajoye New Comment: > Using different links in these two cases should be > sufficient, no need to definie separate email templates. The question is if it is a good thing to put the developer link in the user (which is the only) mail, or make it a private mail. Previous Comments: ------------------------------------------------------------------------ [2006-06-20 13:32:08] wiesemann at php dot net > Yes, because you are normally not supposed to use the > second edit mode, it is only for users. Okay, but for additional comments from myself (or the reply to your question, which is in a different email "template" in the script), the link is "wrong". Using different links in these two cases should be sufficient, no need to definie separate email templates. ------------------------------------------------------------------------ [2006-06-20 13:25:11] pajoye at php dot net Yes, because you are normally not supposed to use the second edit mode, it is only for users. Not sure if it is a good thing to add the developer link to the mail and/or to send a separate mail to the developers. Any comment? ------------------------------------------------------------------------ [2006-06-20 13:19:26] wiesemann at php dot net Small correction: This is true for all packages, not only for bug system bugs. ------------------------------------------------------------------------ [2006-06-20 12:59:13] wiesemann at php dot net Description: ------------ When you are logged in and report a bug about the bug system, you are not asked for a password (that's right so far). But the link you get in the email about this bug (e.g. http://pear.php.net/bugs/bug.php?id=7946&edit=2) points to a page where you should enter a password (which obviously does not exist). Going to the developer variant of this page solves the problem, but maybe the link in the email should point to &edit=1 in the case that a PEAR developer reported the bug. ------------------------------------------------------------------------ -- Edit this bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=1