php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #57097 Bugtracker asks for password that doesn't exist
Submitted: 2006-06-20 12:59 UTC Modified: 2006-12-24 13:43 UTC
From: wiesemann@php.net Assigned: cellog (profile)
Status: Closed Package: PECL bug system (PECL)
PHP Version: Irrelevant OS: Irrelevant
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: wiesemann@php.net
New email:
PHP Version: OS:

 

 [2006-06-20 12:59 UTC] wiesemann@php.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.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-06-20 13:19 UTC] wiesemann@php.net
Small correction: This is true for all packages, not only for bug system bugs.
 [2006-06-20 13:25 UTC] pajoye@php.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:32 UTC] wiesemann@php.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:34 UTC] pajoye@php.net
> 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.
 [2006-06-20 13:44 UTC] wiesemann@php.net
> 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.

There are two cases:

(1) If the reports is answered:

ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at
http://pear.php.net/bugs/bug.php?id=7947&edit=2

(2) The email after I wrote the report:

Edit bug report at http://pear.php.net/bugs/bug.php?id=7947&edit=2

If we have the possibility to differ between the cases whether a developer reported the bug or somebody else, we should modify the links accordingly. That would make life a little bit easier. ;-)
 [2006-12-22 23:09 UTC] cellog@php.net
apparently this is fixed
 [2006-12-23 05:54 UTC] wiesemann@php.net
> apparently this is fixed

No, it is not. Mark it as "Won't fix" (because of the huge changes that would be needed) if you want, but "Closed" is definitely wrong here, as there was only a discussion, but no code change.
 [2006-12-23 14:40 UTC] cellog@php.net
I present to you evidence that this is working.  Here is an email I just received yesterday.  Note that "edit=1" at the bottom

Edit report at http://pear.php.net/bugs/bug.php?id=9205&edit=1

 ID:               9205
 Updated by:       cellog@php.net
 Reported By:      wiesemann at php dot net
-Status:           Open
+Status:           Closed
 Id:               9205
 Type:             Bug
-Package:          Web Site
+Package:          pearweb
 Operating System: Irrelevant
 PHP Version:      Irrelevant
-Assigned To:      
+Assigned To:      cellog
 New Comment:

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.




Previous Comments:
------------------------------------------------------------------------

[2006-10-31 16:34:52] wiesemann at php dot net

Description:
------------
The "quick fix" text for "fixed in release" generates for the "Web
Site" package this URL:
http://pear.php.net/get/Web Site

It should at least escape the space, but maybe also other characters.
(=> urlencode()?)

------------------------------------------------------------------------


-- Edit this bug report at http://pear.php.net/bugs/bug.php?id=9205&edit=1
 [2006-12-24 05:00 UTC] wiesemann@php.net
Keep it closed if you want, but the information mail that I've got after you closed this bug contained these lines:

> ATTENTION! Do NOT reply to this email!
> To reply, use the web interface found at
> http://pear.php.net/bugs/bug.php?id=7947&edit=2

(note the "edit=2" which is still wrong)
 [2006-12-24 13:43 UTC] cellog@php.net
ok, now you're starting to make sense - I didn't realize it was for bugs you had reported.  I have fixed this in CVS, and it will appear in the next release of pearweb
 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Tue Jan 25 15:03:37 2022 UTC