What theme are you using? Where did you download it from? Can you replicate the problem using the default Twenty Fourteen theme with all plugins deactivated?
Thread Starter
zumek
(@zumek)
Thanks for the response, esmi!
I’m using a custom child theme based on Shoestrap.
I just tried what you suggested and it seem like it’s fixed on Android, but IE still the same. I switched back to the child theme and now Android seems to be happy with that. However, I had experienced this issue last week and I was able to fix it (temporarily it seems) by clearing page cache (using WP total cache). But the problem reappeared this week. Clearing cache doesn’t fix it now either. So I’m suspecting that it might not be completely fixed on Android either as the issue remains on IE.
Further adding to the weirdness; I just tested on various versions of IE via Browser stack and it render correctly. But the same version on my local doesn’t work – I’ve cleared cache and flushed DNS.
I also checked the .htaccess file and removed everything but the WP block.
I’m sorry but as you appear to be using a commercial theme, you need to seek support from the theme’s developer/vendor. We do not have access to, nor do we support, commercial products here.
Try http://shoestrap.org/forums/
Thread Starter
zumek
(@zumek)
I’m unsure if this is a WP issue or a theme issue. As it also happens with Twenty Fourteen, could be WP related?
Anyway, I’ll try the Shoestrap forum for anything related. Shoestrap is Open-source BTW, and I created the child theme, so not entirely commercial. But I get your meaning – thanks for your help!
I cannot see any issues in IE when using the 2014 theme. The theme has also been tested extensively across multiple devices including Android. It sounds to me like this is a local network issue. Have you tried using another computer?
Thread Starter
zumek
(@zumek)
Yes, have tested on other networks, machines and browser stack. Not able to reproduce it consistently, which is what’s making it difficult to nail down. I’ve got half a dozen people report the issue, and I can reproduce it consistently on my local, running win 8.1 and IE 11 – fine on Chrome, FF.
