browser incompatibility/session? [SOLVED for now] [EDIT: not solved anymore][EDIT: IE issue with cookies]

[eluser]mradlmaier[/eluser]
[quote author="helmutbjorg" date="1247637049"]I had some problems with login doing the same thing as you mention. Turns out that the form action needed to point to the actual method (even if it is index) in the controller that processes the login rather than to the controller name alone and relying on the default index in CI to work.

So i changed

Code:

form_open('login');

to

Code:

form_open('login/index');

[/quote]

My form action does point to the actual message[EDIT:]method already, so that is not the issue..,

[eluser]JoostV[/eluser]
Did you check if your server clock is set properly?
If it is not set at the right time, some browsers (i.e. IE) will refuse to set session.

[eluser]darkhouse[/eluser]
Your problem is the exact reason we developed and posted this: http://codeigniter.com/wiki/Session_Hybrid/

[eluser]mradlmaier[/eluser]
[quote author="darkhouse" date="1247822224"]Your problem is the exact reason we developed and posted this: http://codeigniter.com/wiki/Session_Hybrid/[/quote]

Did you test it with CI Version 1.7.0, too?

As it is a drop-in-replacemant, I assume it use the sam database schema as the CI Session Class?

[eluser]darkhouse[/eluser]
[quote author="mradlmaier" date="1247839281"][quote author="darkhouse" date="1247822224"]Your problem is the exact reason we developed and posted this: http://codeigniter.com/wiki/Session_Hybrid/[/quote]

Did you test it with CI Version 1.7.0, too?[/quote]

I'm pretty sure we had it running on a 1.6.x at one point. I don't think there's anything in there that will cause any problems. And if there is, let me know.

[eluser]mradlmaier[/eluser]
BTW, this issue also pops up with IE8 under Windows 7 RC1...

Michael

[eluser]mradlmaier[/eluser]
[quote author="darkhouse" date="1247839562"][quote author="mradlmaier" date="1247839281"][quote author="darkhouse" date="1247822224"]Your problem is the exact reason we developed and posted this: http://codeigniter.com/wiki/Session_Hybrid/[/quote]

Did you test it with CI Version 1.7.0, too?[/quote]

I'm pretty sure we had it running on a 1.6.x at one point. I don't think there's anything in there that will cause any problems. And if there is, let me know.[/quote]

As far as I can tell after a brief test, it seems to work with 1.7.0, too

[eluser]darkhouse[/eluser]
[quote author="mradlmaier" date="1248545639"][quote author="darkhouse" date="1247839562"][quote author="mradlmaier" date="1247839281"][quote author="darkhouse" date="1247822224"]Your problem is the exact reason we developed and posted this: http://codeigniter.com/wiki/Session_Hybrid/[/quote]

Did you test it with CI Version 1.7.0, too?[/quote]

I'm pretty sure we had it running on a 1.6.x at one point. I don't think there's anything in there that will cause any problems. And if there is, let me know.[/quote]

As far as I can tell after a brief test, it seems to work with 1.7.0, too[/quote]

Yeah I was implying that I believe we had it working on whatever the last 1.6.x was, 1.7.0 and 1.7.1

[eluser]mradlmaier[/eluser]
:-) BTW, great work and thanks for the contribution to our community

[eluser]darkhouse[/eluser]
No problem, I'll pass along the kind words to my development colleague.

I posted it because I noticed a number of people posting about issues with IE. We're absolutely sick of IE and its seemingly endless list of bugs. It's like as soon as you figure out the work around for something, along comes a whole brand new issue.

For instance, IE8 has a bug with <base> tags, which is a big issue for CI. If you're using javascript files, you have to do 1 of 2 things, either use absolute paths, like /js/jquery.js (note the preceding slash), or place a redundant <base> tag before each script tag. If you don't do either, IE8 will end up loading your javascript improperly, like if your URI is something like mysite.com/products/shoes/123 IE8 will load your javascript relative to that path, products/shoes/js/jquery.js - and obviously that is incorrect.

Thanks Microsoft.