Closed Bug 687288 Opened 13 years ago Closed 10 years ago

Perch on getfirebug.com requires login again and again

Categories

(Websites Graveyard :: getfirebug.com, defect)

defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sebo, Unassigned)

References

()

Details

(Whiteboard: [firebug-p1])

Since it seems, that bug 639438 doesn't get any attention anymore and I am currently not able anymore *at all* to log into Perch to make changes to the website, we definitely need a fix soon now.
Maybe this issue can already be solved together with bug 684704 and bug 650212. Though in the case it is not, this bug should track the changes needed to get the CMS to work again.
Corey - this is a problem we've had for quite a while and it's something we don't have access to.  We need to get someone like shyam or oremj to debug this along with someone from Fred's team so we can fix this.
Assignee: nobody → bhourigan
Sebastian/Michael,

I spent several hours on this and determined that Perch's internal authentication system is not authenticating the username properly. I can further debug this but I think the best thing to do is kick it back upstream to Perch.

In inc/auth.php this test fails:

   if (!$CurrentUser->logged_in() && !$auth_page) {

I can confirm the authentication mechanism is working properly, as when you enter in invalid credentials it displays an appropriate error message.
(In reply to Brian Hourigan [:digi] from comment #2)
> Sebastian/Michael,
> 
> I spent several hours on this and determined that Perch's internal
> authentication system is not authenticating the username properly. I can
> further debug this but I think the best thing to do is kick it back upstream
> to Perch.

Do either of you have contacts at Perch you could reach out to first, or would you like us to start a conversation with them about this?

Sebastian, my apologies for the delay in this..  Trying to get all of the firebug issues wrapped up ASAP for you.
> Do either of you have contacts at Perch you could reach out to first, or would 
> you like us to start a conversation with them about this?
Unfortunately I don't have. As I mentioned yesterday I just got the account info from Neil.

> Sebastian, my apologies for the delay in this..  Trying to get all of the firebug 
> issues wrapped up ASAP for you.
No problem. It's good, that you're there now to take care of that things.
Corey, there was again a long silence. Any update on this?
Would be great, if we got this before the Firebug team releases 1.9 final.

Sebastian
Assignee: bhourigan → nobody
Sorry for poking, but I didn't hear anything again for more than half a year now. And that after Corey promissed to wrap things up.
So I would like to finally get some attention on this, since it's blocking people from changing anything on the getfirebug.com website.

Sebastian
I'd suggest looking for some hope via IRC, perhaps #webdev. But don't quote me on that, it's been a while and I'm not sure what channel would be the best place to ask -- but #webdev would be a good start.
Thanks for the hint, Neil. Will try that.

Sebastian
Is the code for this up somewhere that I can setup a local environment? I'm not yet committing to fixing this, but I'd like to poke.
Yes, in the Mozilla Subversion repo.

Didn't have time to contact people on IRC yet. Should I wait for you?

Also I want to note that there is a fresh new Perch 2 release. Maybe updating to it would help?

http://grabaperch.com/blog/archive/perch-2-requires-php-52

Sebastian
Heh, someone already asked on #webdev and that's how I came about this bug :)
I see. :-) I guess that was Honza then. Let me know if you could find out something.
Btw. the latest version of Perch I could download was 1.8.4. Don't know if it's possible to get the latest version.

Sebastian
Any progress on this one?

It would be really helpful for the Firebug team if Sebastian has the access.

Honza
Whiteboard: [firebug-p1]
This obviously got fixed lately. Thanks to whoever did that.

Sebastian
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Websites → Websites Graveyard
You need to log in before you can comment on or make changes to this bug.