TYPO3 Core

Can't reproduce with trunk.

Can you give example URL?

... and also not with an 4.2 installation with newloginbox.

Works for me. Your IE8 seems to have a problem (okay.. it is a problem by definition.. but it has at least one more :-P)

You should try to install a fresh windows in a VM or maybe try another PC.

This Problem still remains.

I can reproduce this on 2 Virtual Machines (XP, VISTA) and a real XP. And I have no clue what is going on.

But the low response to this issue gives two options:

a) FE login is not too common
or
b) Some systematical mistake I make on my installations.

I keep on trying...

I've got precisely the same problem! I'm running typo3 4.2.6 and at first instance the login seems to work, but after that I'm kicked out for some reason.

Anyone got a solution?

I had similar problems with safari recently: Turned out the script cookieManager.js (needed by efa_fontsize.js, included in YAML) was the problem. The script sets cookies for one level top of your current domain.

I was searching for a solution, but many posts on the internet end up without a solution.

In my case I don't have the CookieManager.js script, because I don't have efa_fontsize installed. Other solutions like changing the LOCKIP settings in the Typo3 install didn't help me.

What do know is that IE8 also has trouble with the BE login. I always get the message "no user logged in! Sorry, I can't proceed then". Sometimes Firefox in windows has the same problem. Mac browsers don't have this problem.

Maybe someone has the final solution?

What I'm reading here is that only IE causes trouble.

So please check your TYPO3 installation if there's any JavaScript code (custom one configured by TS or brought by an extension) accesses/modifies your typo3 FE cookie.

If this doesn't bring up any result, please capture your http traffic (e.g. using wireshark), to see what cookie (and its parameters) the server is sending and the browser is returning back.

Before attaching such a capture file here, please make sure to remove transferred passwords and/or hostname due to security reasons.

We had the same issue but defining the cookies domain in the localconf.php seems to have resolved it.

$TYPO3_CONF_VARS['SYS']['cookieDomain'] = 'youdomain.com';

What was very odd was that we did not have the issue on a development version of the site, which was located at: devversion.yourdomain.com, it only showed up on the live version - yourdomain.com

We did further notice this:

cookies from live site have:
fe_typo_user - domain:.yourdomain.com
PHPSESSID – host:yourdomain.com

vs test server

fe_typo_user - host:yourdomain.com
PHPSESSID – host:yourdomain.com

So in live server fe_typo_user relates to domain, but on test server to host.

--> both sites were on the same server, just the dev version was in a subdomain.

I think this one could be related to #20757 - I could reproduce the behaviuor with IE8, after switching to Compatibility Mode. Without Compatibility Mode, there is no problem in my test scenario.

Can you confirm that you are using IE8 in Compatibility Mode when having the problem to be logged out after the first click in frontend?

@Ralf Hettinger: After Switching to Compatibility Mode I'm experiencing the same problems in FE & BE. In problem 0011538 asks if javascript is giving errors after login in: yes it does. My Jquery menu didn't load in IE8 and IE8 (compatibility mode).

@Simon Browning: Doesn't matter for IE8. Firefox only takes this feature after removing all cookies.

@Marcus Krause: It does not seem to load in IE8 when it's activated. Jquery deactivated does not seem to help for loging in. Which part of the wireshark analysis do you want to have? It's quite a bit... I'm guessing only the filtered POST and GET part?

@all review: Not only IE is giving me headache, also firefox in windows and mac are sometimes very struggling with loging in... after clearing the cookies and a few times trying it helps to log in, but in my opinion this takes to long in comparison what it used to do...

check for phpmyadmin - uninstall and try again.

@ssteffan Kamper: What do I have to check in phpmyamin? Do I need to reinstall typo3? What do you mean?

Do you have phpmyadmin extension installed?

I'm not using this extension...

@Steffen Gebert: yes, phpmyadmin is in place. Good idea, that it's session handling might interfer with TYPO3. Will have a look at it - thx for the idea!

Edit: EXT:phpmyadmin doesn't make a difference here for IE8 Compatibility Mode + fe_user session - it still breaks.

Hi I had exactly the same problem on IE8 and Firefox. I could resolve it like this:

I set the variable: [cookieDomain] in Install tool to ".mydomain.ch".
It was empty before and now the frontenduser stays logged in.

@Cyrille Fl?ckiger: I tried that before, but without luck. I'm using a multidomain typo3 package, and with that configured as mentioned in the configuration tool, it didn't work.

Recently I got an email of someone who had the same problem and thought it was mentioned over here:

http://bugs.typo3.org/view.php?id=10566&nbn=8
http://bugs.typo3.org/view.php?id=10567

They mention that typo3 4.3 alpha3 would fix it. Anyone tried this?

@christiaan uythoven:
My version is 4.2.8.
If you're using a multidomain typo3 package. There's some advice how to set the cookieDomain-Value by a regular expression to cover the situation with multiple domains. Don't know if you did it that way or not. Just another suggestion that might help finding the solution.

The failed browser detection of IE is already fixed in 4.2.8

@Cyrille Fl?ckiger: I did the solution you mentioned, but without any result...I'm able to login in the domains, but it sometimes takes a while with browsers on my MAC. Firefox on windows hesitates a long time, but does let me login. IE8 definitely does not allows me to login, since it kicks me out every time.

Without a capture of headers that are sent (set-cookie,cookie) there's no way to determine what goes wrong here.
I'm unable to reproduce. Whoever has the problem, check if no JS code interferes with cookies and capture your traffic.

Like Simon already pointed out, there might be a problem with the host-settings in the cookie (domain only vs. domain+subdomains)

In my TYPO3 enviroment I found lots of pages with different login settings on the page propertys.
changing this to 0 (no special login-handling at all) solved /my/ problems.

Mybe all of you reporting prpblems here, check on your page on tab access the loginmode.
You should check the TSconfig options for this feature, too :
(loginmode ist used in conjuction with this options)

config.sendCacheHeaders = 0
config.sendCacheHeaders_onlyWhenLoginDeniedInBranch = 0

Hope for all of you this ist the mistake. For now I am happy. Thanks to all of you!

Christian.

Check #21511 as well.

Please check #22084 for the issue of FE-Logins in IE8. RFC is in core list, review, test and give you +1 there if the patch solves your problem.