This topic has 5 replies, 2 voices, and was last updated 7 years, 4 months ago ago by Rose Tyler
Hello, capable, friendly team 8theme support.
A customer reported missing information on a page that had tabs generated by an [etheme] shortcode, when viewed on MS Internet Explorer. (We might have ignored that browser, if he weren’t a partner in their firm.)
That was news here. When we looked into the matter, it was more widespread than the initial description. On IE11, the Xmarket header submenus do not display, the category tree is fully open (never collapsed), and the tabs for the product “Description” and so forth are not visible, much less selectable.
I then verified that the theme demo at https://www.8theme.com/demo/xmarket-wo/ does work correctly on IE.
To troubleshoot the problem and make sure that we had not broken the theme, I made a staging server copy, left all plugins intact, and deleted the child theme. The IE issues remained.
I removed Xmarket 2.3.0 and upgraded to v. 2.3.1, along with LayerSlider 6.5.5, and the IE issues also remained.
Then, I removed the Xmarket theme and reinstalled 2.2.1, and the IE issues were fixed.
Therefore, my best guess is that the demo is still running 2.2.1, and code introduced by 2.3 broke the IE display. I didn’t see any console errors that point me to an easy solution.
Could you please look into the matter? We’re running Xmarket on two client sites, so far, which I’ll list below.
Hello,
Please provide wp-admin and FTP access in Private Content.
Regards
I’ve checked these problems on our test site and seems these our bugs, so please check your email and replace this file /xmarket/js/script.js.
If you will face any problem after that, please contact us and provide access.
Regards
Thanks, Rose. Once again, you’ve taken responsibility and provided great service in a short turnaround. A pleasure doing business with you.
Have a great weekend.
Hello,
You’re welcome!
Thanks for being our customer.
Regards
The issue related to '‘Menus, Tabs, Category Tree Broken on MSIE in 2.3+’' has been successfully resolved, and the topic is now closed for further responses