- This topic has 13 replies, 6 voices, and was last updated 1 year, 3 months ago by Tom.
October 26, 2020 at 11:52 am #1505204Clayton
External Fileoption chosen for the Dynamic CSS Print Method option it doesn’t update. With Autoptimize deactivate the external file option seems to work fine.
Since Autoptimize is such a popular option for caching and minification with over a million installs I thought it was worth checking on this to see if there is something to be done.October 27, 2020 at 2:17 am #1505833DavidStaffCustomer SupportOctober 27, 2020 at 4:29 am #1505975Clayton
Yes. For example the color of the footer bar or the wrapper width.October 27, 2020 at 7:08 am #1506154DavidStaffCustomer SupportOctober 27, 2020 at 7:58 am #1506520Clayton
Yes, I have cleared the cache. I try not to as well but some changes need to be made after the fact. Okay, well since I know what’s causing it I can avoid it but I wanted to let you know that the external css print method seems to be conflictingzOctober 27, 2020 at 9:53 am #1506680TomLead DeveloperLead Developer
Strange, I would have thought that Autoptimize would clear its cache whenever changes are made (Customizer saved etc..).
We’ll look into whether or not this is something we can fix.October 27, 2020 at 10:06 am #1506701Clayton
That’s a good point. I’ll double check with them now that I know what the specific conflict is and maybe that can do something about it on their end. By the way really loving GP 3 and GB.October 27, 2020 at 10:56 am #1506780Clayton
Figured it out. By default Autoptimize excludes the
wp-content/uploadsdirectory which is where the external CSS file is stored by GeneratePress. I’ve removed that exclusion rule and it all seems to be working as expected. Just wanted to post here just in case anyone else runs into the same issue.October 27, 2020 at 1:58 pm #1506987TomLead DeveloperLead DeveloperDecember 6, 2020 at 8:53 am #1569443Rylan Urban
Thanks. I had the same issue. Removing
,wp-content/uploadsfixed it.March 11, 2021 at 4:05 pm #1691818acela
Gosh, thank you! I was just about to post/ask about this. Using Autoptimize with its default settings plus GeneratePress’ recommended settings was not aggregating
generatepress/style.min.cssand I couldn’t figure out why…
Wasted a bit of time trying to sort it out and didn’t think to review AO’s default “exclude” field.
In fact, the settings screenshot on GeneratePress’ help page even shows the
wp-content/uploadsdirectory as excluded. Tom and David, do you think it’s worth addressing/fixing this there? It could help other folks too, and improve customer site optimization by not loading this additional file separately.
Thanks!March 11, 2021 at 7:51 pm #1691915ElvinStaffCustomer Support
Thanks for letting us know. Glad you got things sorted.
As for fixing this: It’s not really a theme issue as it’s on Autoptimize’s side of things.
But yeah, I think this is worth atleast a mention for users generating external CSS. We’ll see when we can add this in on the documentation. 😀
A wise man once said:
"Have you cleared your cache?"March 12, 2021 at 7:24 am #1692670acela
Thanks Elvin! You’re absolutely right that it’s not a GP theme issue at all.
However, Autoptimize is extremely popular with over 1 million installs (you even use it on your own site) and GP’s generated file will not be included in CSS aggregation with AO’s default settings.
So, highlighting (“fixing”) this on your AO recommended settings help page so that GP users can be sure to achieve maximal optimization of the theme is great. 🙂March 12, 2021 at 9:41 am #1692828TomLead DeveloperLead Developer
Agreed. I think it may even be worth looking at moving the file outside the
For now, we’ll mention this in our documentation to prevent further wasted time.
- You must be logged in to reply to this topic.