[wp-trac] Re: [WordPress Trac] #7322: Unable to login after 2.5.1 to 2.6 upgrade - returned to login screen.

[WordPress Trac]

#7322: Unable to login after 2.5.1 to 2.6 upgrade - returned to login screen.
----------------------------+-----------------------------------------------
 Reporter:  dolemite        |        Owner:  anonymous
     Type:  defect          |       Status:  closed   
 Priority:  normal          |    Milestone:           
Component:  Administration  |      Version:           
 Severity:  normal          |   Resolution:  invalid  
 Keywords:                  |  
----------------------------+-----------------------------------------------
Comment (by Otto42):

 Replying to [comment:15 trisweb]:
 > Excuse me? This is not a support problem, several people have verified
 it and it is a bug introduced in 2.6!

 No, it is not. It is a support problem. If it was a bug, then it would be
 a bug on more than a handful of cases. Yes, that is correct, a handful.
 Less than 50 people have reported the problem on the support forums, and
 2.6 has been installed several thousand times.

 The new login cookie system sets new cookies, however it also READS those
 new cookies. There is no bug there.

 I have been able to duplicate the cookie problem through an unusual series
 of upgrade steps. However, clearing cookies solves that problem, every
 single time. This problem is characterized by the fact that using an
 alternative browser generally works.

 It is also the case that some overprotective firewall and anti-virus
 systems running on the users local machine prevents the cookies from being
 set or cleared properly. In these cases, the solution is to fix the local
 machine.

 I've yet to see a single case of a legitimate bug in this area. I did have
 one case where I could not immediately identify the issue, however before
 I could debug it further, the owner of the site erased it and reloaded and
 got it working that way. I suspect misloaded files in that instance.

 See, a bug is not "it's broken for a bunch of people". A bug is "here is
 an error in the code at this specific location".

 Until it is verified and can be duplicated reliably, it is not a bug. In
 that case, it is a problem that you are having... and those belong on the
 support forum.

 When you have identified the cause or can give ''repeatable steps'' to
 duplicate it, then feel free to chime in here about it.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/7322#comment:17>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software