I installed FFox22 and now cannot login to my own website anymore - what should I do?
I installed FFox22 and now cannot login to my own website anymore http://reverd.com/login My question is simple: is there a problem with our code (probably not since it is working well in all other browsers) or is it the New FFox22 browser problem. If it is a browser problem it should be fixed rather soon otherwise people will have to use alternative browsers. It is not proper to advise people to all that additional clicking and cleaning in order to login - no way! please advise.
Thanks, M
Toutes les réponses (6)
Hello,
Many site issues can be caused by corrupt cookies or cache. In order to try to fix these problems, the first step is to clear both cookies and the cache. Note: This will temporarily log you out of all sites you're logged in to. To clear cache and cookies do the following:
- Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
- Under "Time range to clear", select "Everything".
- Now, click the arrow next to Details to toggle the Details list active.
- From the details list, check Cache and Cookies and uncheck everything else.
- Now click the Clear now button.
Further information can be found in the Clear your cache, history and other personal information in Firefox article.
Did this fix your problems? Please report back to us!
Thank you.
This is the validation summary of that page:
What exactly is the problem?
Don't you see anything if you open that URL or doesn't anything happen if you click the Login button?
Start Firefox in Safe Mode to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).
- Do NOT click the Reset button on the Safe Mode start window or otherwise make changes.
Thank you folks for your quick response. All these tips might be useful but the point is website user experience. If the new browser causes the problem and I have to tell everyone to do all that clicking and to get rid of all cookies (I will not delete my cookies. some are old 3 years and more and I do not even remember how to access those site without cookies), so if the browser is the issue I would rather tell the "Hey switch to better browser"... Looks like they killed the browser. It is unfortunate but we have to do what we have to...
Thanks anyway! M
To get into a site where the cookie expired or got lost, just log in again. You will get a new cookie.
I have Firefox 20.0 running on Ubuntu 10.04, the latest version currently available through the Canonical code repository for that operating system, and it's exhibiting the same problem. As best I can remember, the issue with not completing usernames and passwords started with release 19, several months ago. Stored login credentials still work with Mozilla SeaMonkey 2.20 on sites where Firefox just sits there and does nothing, so I can conclude it's the browser, not the site. Even though SeaMonkey has adopted much of the Firefox code, fortunately it hasn't adopted whatever the Firefox team did to break this functionality -- yet. I've also noticed that when I enter a new password to a site for which a password is already stored in Firefox, it no longer acknowledges the change with a dialog box, asking me whether i want to replace the old stored password with the new one. I also find sites, like the Yahoo! Mail login, where I type the username and password, and click the login button, and Firefox does nothing. So help me (!), I need to shut Firefox down and restart it to be able to log into Yahoo! Mail. Firefox is now broken, plain and simple.
However ... there are a few sites that have apparently changed the way logins work that break automated login -- perhaps deliberately. It's a problem in both Firefox and SeaMonkey, particularly where a Javascript pop-over window is used to log in, or where a server-side script generates the login form and "salts" the username and password fields with random characters so the browser can never recognize them and is thus unable to autocomplete the fields. The Web designers who do this may think they're improving site security when, in fact, all they're doing is annoying users and driving traffic away, or encouraging users to use the same login and password everywhere, because they no longer have their browser helping them remember 326 unique logins and passwords on different sites.
Modifié le