- This topic has 4 replies, 2 voices, and was last updated 8 years, 10 months ago by
.
- Posts
Hi Dan
Thanks for your support, it’s most appreciated.
I’ll test with KeyCDN tomorrow and try figure out where the problem is.
Just an idea; the Customizer outputs its styles inline in the document
head, Certain caching plugin settings could in theory negatively impact this or perhaps move the inline block into a compressed stylesheet, perhaps above the theme’s style.css file in terms of cascading order. Are you using a caching plugin along with KeyCDN? If the answer is yes, did you disable the caching plugin and the CDN in testing or just the CDN?With regards to your child theme, the theme slug changes when we activate a child theme in WordPress. This unfortunately, cases the Customizer and Menu Location settings to reset. This is an expected result. I have seen a workaround for this problem. If it sounds like this is the core of the challenge, let me know and I’ll investigate the workaround further.
I’ll reply ASAP tomorrow (GMT+2).
Thanks 🙂
Thank you Andrew!
I am just using caching on the server level, via .htaccess. I do have the Autoptimize plugin set up.
Here’s the results of my testing:
Autoptimize On, KeyCDN Off: Works as expected
Autoptimize Off, KeyCDN Off: Works as expectedAutoptimize On, KeyCDN On: Breaks all settings in Customize > Theme Design (goes to defaults, although the Customize menu shows correct settings)
Autoptimize Off, KeyCDN On: Works as expected
Based on this, it looks like the easiest thing to do would be to exclude that in-line CSS from Autoptimize. What should I be looking for in the original code, to exclude?
Ok, found an option to exclude inline CSS from Autoptimize, and that did it. Looks like it was the combination of both that gave me the issue. Thank you very much for your help!
Dan
You must be logged in to reply to this topic.