- This topic has 7 replies, 2 voices, and was last updated 4 years ago by
Sebastian.
Author | Posts |
---|---|
lloydsilver
May 13, 2019 at 9:38 pm
|
If I try to go to Microthemer for any page on the site, I’m getting an error: This site can’t be reached. With a message code ERR_CONTENT_DECODING_FAILED Haven’t seen this before on any site. |
lloydsilver
May 13, 2019 at 9:42 pm
|
Happens in Chrome and FF. And on multiple computers. |
Sebastian
May 14, 2019 at 9:04 am
|
Hey, I think you can solve this by going to the standalone Microthemer > Preferences page (via the left-hand menu in WordPress). Set Gzip the Microthemer UI page for faster loading to “No”. Your server configuration may have been updated recently if this problem has just started. Please let me know if the problem persists. Thanks, |
lloydsilver
May 14, 2019 at 5:43 pm
|
Hmmm. I’m seeing a blank page on Microthemer > Preferences |
Sebastian
May 14, 2019 at 6:31 pm
|
Oh dear. Perhaps there is more to this than I thought. Would you mind providing access for the affected site via our secure contact form so I can troubleshoot this? Thanks, |
Sebastian
May 15, 2019 at 9:57 am
|
Hey Lloyd, Thanks for sending access details. I’ve managed to get the MT interface to show, but there is a conflict with bootstrap. Bootstrap is currently loading on WordPress admin pages. Bootstrap should only load on the frontend to avoid such conflicts. Or if a plugin loads it for the admin area, it should only load on that plugin’s pages. Bootstrap has a .hidden { display:none !important; } rule which is why Microthemer’s standalone preferences page is blank. Also, MT’s icons are messed up. And the input fields don’t show. This is the problem stylesheet: https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.css Have you enqueued this Bootstrap stylesheet via your theme’s functions.php file? If so, you can make the enqueue rule conditional so it doesn’t load in the admin area:
Or do you think it might be a plugin? I which case, can I disable some of your plugins to isolate the cause? Thanks, |
lloydsilver
May 17, 2019 at 11:09 pm
|
Yep, that was it. Thanks for troubleshooting. I should have known better. Rogue plugin. |
Sebastian
May 20, 2019 at 9:40 am
|
OK great, glad we got to the bottom of it! |