Thread

Hey all,

Wow, feels kinda weird posting in the Legacy Forums 😉, but I have a client on 1.6.9 Core, and some strange stuff is happening.

First, when he tries to login in *Firefox* using the url http://foobar.com/system the page title says “Redirect”, but nothing ever happens after that. It just remains a blank screen.

Now on all my computers, this doesn’t happen. And any other browser he uses, it works fine. But, he wants to use Firefox.

Along with that, if you go to http://foobar.com/system/index.php, it shows the login screen fine.

So my question is, is there some setting or feature he could have messed up in Firefox, that prohibits EE to run its course? (Because it is obvious its nothing wrong with ExpressionEngine directly, but with this fiasco is makes me look like an idiot 😉)

In conclusion, when he does try to login, it won’t log him in. It just refreshes the login screen, and gives no error messages whatsoever, and the Control Panel Log states he is logged in, but it doesn’t work for him. Again, this is only on his computer and only on Firefox.

So if you guys no of anything I could try that would be great!

Thanks!

I’ve may have had similar issues rise up in the past. Has he tried clearing the Firefox cache? Though it might be a timesaver to have him (a) backup his Firefox bookmarks and (b) remove Firefox from his machine and then (c) reinstall Firefox. I’ve had no problems accessing 1.6.9 Core sites with Firefox.

Thanks for replying!

Yeah, he cleared his cache and temporary internet files.

I was considering telling him to reinstall Firefox, so I’ll see if he can do it.

Yeah, 1.6.9 works fine for me, and works fine for him on every other browser, except Firefox.

Thanks for the help.

From a troubleshooting standpoint, I wonder if one might see different results if he tried to log in while the browser was set to Private Browsing? It it’s a cookie or a cache issue, a Private Browsing session might reveal something. I’m assuming Private Browsing sessions bypasses the cache and temp files entirely.

This is probably not likely, but I once had the exact problem you are describing with Firefox.  It was because I had disabled meta redirects.  This is an option in the Firefox Web Developer Toolbar (Disable > Disable Meta Redirects).  Any chance your client has that installed and managed to select that option?

Thanks to both of you for responding!

I don’t think he has the Web Dev Toolbar installed. But I’m pretty sure he’s got something screwy going on with his Firefox setup.

I’ll see if he can get it to work in private browsing.

Thanks again guys!

Hey Kyle

Did you manage to resolve this Firefox issue? I have a site user with a similar Firefox problem. He can sign into the control panel, and use the control panel, but his problem is that any code within {if logged_in}...{/if} tags won’t show up for him in Firefox.

This is an issue, because I use that code when developing the site so that only logged in members can view the part of the page I’m working on or have prepared for the client to view before making it public.

Did you get anywhere with your issue?
Scott