Support » Plugin: Autoptimize » Does cache clear after making changes in Customizer?

  • Resolved Clayton Chase

    (@claytonchase)


    Hey guys,

    I have a question. Does cache clear after making changes in Customizer?

    Also, there seems to be a conflict with a theme – GeneratePress. This theme has an option in Customizer that allows you to dynamically print the CSS via an external file. When that setting is enabled changes made in Customizer don’t get changed even after clearing the Autoptimize cache.

    I should add that regenerating the CSS in Customizer makes no difference.

    Screenshot: https://imgur.com/a/vHXPo9A

    I’ve contacted the theme developer and they are looking in to it as well but I thought it would be worth sharing with you guys just incase it’s something you can address.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Optimizing Matters

    (@optimizingmatters)

    clearing Autoptimize’s cache should not be needed, but you might want to try disabling “also aggregate inline CSS” claytonchase?

    hope this helps,
    frank

    Thread Starter Clayton Chase

    (@claytonchase)

    Hey @optimizingmatters ,

    I’ve tried that and it doesn’t seem to make a difference. It’s definitely related to that setting in GeneratePress but that’s not your guys issue. Not a huge issue but just wanted to see if I was missing something. Thanks for the quick response and developing such a solid caching solution for all!

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Ah, it’s an external file, missed that. I assume it is located in wp-content/uploads which AO excludes from aggregation by default, try removing that exclusion maybe? Alternative could be to add !important flags to avoid your CSS being overruled by other CSS.

    Thread Starter Clayton Chase

    (@claytonchase)

    Removing the wp-content/uploads from the exclusion did it! Thanks @optimizingmatters !

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    Great! Now this is excluded by default because many-a-pagebuilder drop page-specific CSS there, which when aggregated might cause Autoptimize cache misses and thus a faster growth of the AO cache, so keep an eye on cache size maybe 🙂

    have a nice day!
    frank

    Thread Starter Clayton Chase

    (@claytonchase)

    Makes sense! I’ll keep an eye out.

    Thanks again!

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.