I have a usercontrol/macro that has a normal .NET LoginControl, I have it on a normal Umbraco page and if I use Chrome, Firerfox, Opera, Safari it works fine. I click login and I either login or get an error message for incorrect credentials etc..
BUT it will not work in IE?? (I'm using IE8) .. If I click the login button, nothing happens? I'm miffed at the moment... Just wondering if anyone else has had similar issues?
Found this: http://forums.asp.net/t/1121401.aspx - suggestions are that it could be related to Google AdSense? But there are a few other suggestions on that forum topics too!
FIXED!! And you will not believe what it was........
I am putting this solution here in case anyone else has the same issue!!
So I had a standard login control and I had no JS errors but when you clicked the login button nothing happened in IE, but worked in Chrome fine got error messages etc......
After looking through the source, I noticed one of my JavaScript includes was being self closed as it was in an XSLT macro (Here is part of the XSLT)
It will try to revert all the self-closing tags, apart from <img>, <hr> and <br>, etc. Not sure if it works with v4.5, but it's a HttpModule, so I see no reason why not.
IE Login Problem
Just had the strangest problem!
I have a usercontrol/macro that has a normal .NET LoginControl, I have it on a normal Umbraco page and if I use Chrome, Firerfox, Opera, Safari it works fine. I click login and I either login or get an error message for incorrect credentials etc..
BUT it will not work in IE?? (I'm using IE8) .. If I click the login button, nothing happens? I'm miffed at the moment... Just wondering if anyone else has had similar issues?
Hi Lee,
What type of control are you using for the submit button? Is it a Button or ImageButton?
I've heard cases where ImageButton can cause a problem and not trigger the OnClick event.
Cheers, Lee.
Its a button fella? Its just a normal loginControl which is why I'm a little miffed :S
Hmmm... any other JavaScript errors in IE?
Found this: http://forums.asp.net/t/1121401.aspx - suggestions are that it could be related to Google AdSense? But there are a few other suggestions on that forum topics too!
Good luck! Lee.
FIXED!! And you will not believe what it was........
I am putting this solution here in case anyone else has the same issue!!
So I had a standard login control and I had no JS errors but when you clicked the login button nothing happened in IE, but worked in Chrome fine got error messages etc......
After looking through the source, I noticed one of my JavaScript includes was being self closed as it was in an XSLT macro (Here is part of the XSLT)
<script src="{$currentPage/ancestor-or-self::node [string(data [@alias = 'areaJavaScript'])!=''] [position()=1] /data [@alias = 'areaJavaScript']}" type="text/javascript"></script>And it was producing
<script src="/scripts/my.js" type="text/javascript" />I changed the code to
<script src="{$currentPage/ancestor-or-self::node [string(data [@alias = 'areaJavaScript'])!=''] [position()=1] /data [@alias = 'areaJavaScript']}" type="text/javascript"><xsl:text> </xsl:text></script>And now it works fine in IE!! How frustrating.... This caused the login control to just not work!!
Hip-hip-hurray!
Bet you love XSLT even more now? ;-) LOL
Glad you got it sorted Lee - if only you could mark your own reply as the solution!
Cheers, Lee.
lol indeed I don't love it ;) Yeah now you are all powerful MVP n' all, can't you suggest that feature to the 'firm'
If only! But that's a specific XSLT issue, not even a bug really. Frustrating I know.
Take a look at the ComplianceFilter for Umbraco module, it might be what you're looking for?
http://compfilter4umbraco.codeplex.com/
It will try to revert all the self-closing tags, apart from <img>, <hr> and <br>, etc. Not sure if it works with v4.5, but it's a HttpModule, so I see no reason why not.
Cheers, Lee.
Yup, IE will also throw a fit if you have a self closing DIV as well (even though its technically valid).
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.