|
Has anyone had any problems with IE lately? I just tried to go on my site on IE9 and the site is completely broken. I tried going on shoppica2.com and it works completely fine. I don’t have any core changes to my site, and if I do it’s all text related. If anyone can help, I’d greatly appreciate it!
Site: http://www.gunsafari.com
OC 1.5.2.1, Shoppica 2.0
Also, I reuploaded the original screen.css file and it’s still giving us problems. The site sometimes works when you go to the home page, but when you try to go on any product or try to checkout the whole site becomes broken. I also have a CDN (which I tried disabling) but it’s still giving us problems. I know how crappy IE is, but the fact of the matter is most people use it for some reason! Any info would be appreciated, thank you in advance!
|
|
|
My first shoppica 2 installation was not working properly with IE9 and also had a lot of bugs with older IE versions , I found out that some modifications in the css and js files resolved the issue , I copied the files after it rendered from the browser to remove the php variables from it and it worked , just make sure to leave the variables located in the beginning of the file which are essential to load some theme preferences.
A few days ago when I installed shoppica 2 again it worked with IE9 and older IE versions without modifications , I’m trying to figure out what happened but I know I don’t like how the css and js files are php files with variables , I think the issue comes from there.
|
|
|
Thanks for the reply! Do you know which piece of code needs to be altered? Thanks in advance!
|
|
|
I just updated to Shoppica 2.1 and still having the same issues with IE. I posted some pics below:
|
|
|
I just re uploaded the stylesheet and javascript folders and I am still having the same issues. I also tried disabling everything on vqmod and it doesn’t help. I deleted a few unnecessary extensions as well, and that doesn’t solve it either.
I just added a new subdomain and installed shoppica on 1.5.3.1 and it works fine — guns.gunsafari.com. Is there anything else I can do to try and resolve this issue? Any help would be greatly appreciated!
|
|
|
Ok, just tried and changing the theme to the default theme and that’s giving me problems as well. Looks like it’s most likely a core issue than anything else. I don’t think it’s a shoppica issue, I will see what I can do to resolve this issue and post my solution here.
|
|
|
I found the solution, it was an error on the site. Here was my fix:
There was an extra header text (<!– You can login or create an account. –>) which messed up IE Document mode. The extra text was added into catalog/language/english/common/header.php file outside of php code and it was displayed in header text. All you need to do is delete that and make sure no extra text is added outside of php.
|
|
|
Hi,
Doctype declaration should always be at first place for IE, or you risk to go into quirk mode (the reason for messy design).
Other common reason for going into quirk mode is UTF-8 with signature (BOM) encoding of language (or other core) files.
Glad you’ve managed to solved the problem. We really haven’t noticed this extra row at first sight.
Best,
ThemeBurn team
|
|
|
…. hi,
OC 1.5.3.1
Shoppica 2 v2.1.3
my URL: aczesorios.com
exact same problems… I can see it perfectly in FF and Chrome but in IE 9 is a disaster.
Please see attached pics. Note that FF is showing also OK.
Checked brotsky solution but I don’t seem to have any code outside php in my /catalog/language/english/common/header.php file
Can you please help?… I’m quite lost and panicking now cause I myself use FF and Chrome while developing so I haven’t checked IE until now… and the shop is supposed to be open within a few weeks from now!
Thanks a lot
****************************
ISSUE CLOSED
****************************
SILLY ME!!!!.
I had edited “\catalog\view\theme\shoppica2\template\common\header.tlp” to include a couple of customizations and, in order to remember what I’ve change I tend to include a comment -so to speak- in line 1 of the file. I was wrongly commented as I used “<!–" instead of "<?php" followed by "//comment". Anyhow, it's weird that FF and Chrome were not complaining while IE did!
-
This reply was modified 4259 days ago by
 enric.
|
|
|
Hi,
Sometimes IE is more strict, when it comes to html rendering 
The same results can be caused by wrongly used UTF-8 with signature encoding, as we’ve explained a few post above.
Best,
ThemeBurn team
|
|
