-
AuthorPosts
-
July 26, 2016 at 7:24 pm #665442
I’m running Chrome v51, WP v4.5.3 and Enfold v3.6.1 on a new MacBook Pro.
On chrome, the admin dashboard doesn’t appear to be loading the CSS. It’s not styled. It works fine in Safari. I have several other client sites that don’t have an issue, but this is the most recent site I’ve built.
I found several people who had this issue with Chrome 45, but none more recently, and those fixes didn’t work. Any ideas?
Thanks
July 26, 2016 at 8:12 pm #665449Hey jstonestreet!
That happens on chrome, have you tried firefox?
Does it still happen?Can you please provide us backend access of the web site, so we can give a look at the issue?
Cheers!
BasilisJuly 26, 2016 at 9:42 pm #665495I haven’t tried Firefox, but it does work in Safari.
July 27, 2016 at 10:33 pm #665974July 27, 2016 at 11:57 pm #665993Woops. Minor detail…
August 1, 2016 at 3:00 am #667096Hi,
Did you install any plugin prior to this issue? Please access the wp-content folder via FTP or cpanel then rename the plugins folder temporarily. This will deactivate all plugins.
Best regards,
IsmaelAugust 1, 2016 at 6:08 pm #667379I manually deactivated all of the plugins through the wp admin, but that didn’t fix it.
Changing the plugins directory name, then changing it back fixed it.
Very odd. Thanks for the idea.
August 4, 2016 at 5:32 am #668380August 4, 2016 at 5:53 pm #668673It fixed most of it. The left nav on the enfold theme setup page and the plugins page were still not displaying correctly. So I changed the name of each plugin directory separately. That fixed it. Then I changed each plugin directory back one at a time and tested it, but I wasn’t able to reproduce the issue. Everything appears to be working…for now. This is an odd one.
August 5, 2016 at 8:03 am #668872Hi,
Ok, glad you got it working though. We’ll keep the thread open in case you should have any further problems on the topic.
Best regards,
RikardAugust 9, 2016 at 6:33 pm #670472This issue is back again. Nothing changed on the site and it only happens in chrome. It works fine in Safari and the front end looks fine in both browsers. Am I the only one seeing this issue?
August 10, 2016 at 4:00 pm #670891August 12, 2016 at 10:29 pm #672110Sorry. Thought we got hacked so I reset all the passwords.
August 15, 2016 at 6:01 am #672504Hi,
Could you set the account to admin rights please? I get this message when trying to access the WordPress backend:
You do not have sufficient permissions to access this page.
Thanks,
RikardAugust 15, 2016 at 4:37 pm #672793Done. Sorry about that.
August 16, 2016 at 6:54 am #673021Hi,
Great, thanks. I see your problem and you are getting a bunch of errors on the site, could you try to deactivate all plugins to see if there is a conflict from any of them please? If you should be unable to do so from the backend then you can go to /wp-content/plugins via FTP and change the name of that folder temporarily in order to deactivate all plugins. Also please make sure that you are running the latest version of the theme (3.7.1): http://kriesi.at/documentation/enfold/updating-your-theme-files/
Best regards,
RikardAugust 16, 2016 at 2:44 pm #673281Please refer to earlier posts. We’ve already tried the plugin route and it worked briefly but the issues came back. I just updated the theme to the latest version and the issue is still there in Chrome but it still works fine in Safari. I’m also using a Macbook Pro if that matters.
I’ve launched 3 more sites using Enfold since this one without issue.
August 20, 2016 at 4:19 pm #675037Hi,
Try disabling
CONCATENATE_SCRIPTS
by adding this line to wp-config.php:define( 'CONCATENATE_SCRIPTS', false );
Best regards,
JosueAugust 20, 2016 at 7:08 pm #675063Looks like that worked. However, deactivating the plugins worked for a while but then the issue came back.
Thanks for your help. I would have never figured that one out on my own.
August 20, 2016 at 8:24 pm #675076Glad it worked, the error was the following:
Error 330 (net::ERR_CONTENT_DECODING_FAILED): (Google Chrome)
So i though disabling WordPress admin script concatenation/compression would fix it.
Best regards,
Josue -
AuthorPosts
- You must be logged in to reply to this topic.