[Resolved] Dynamic CSS Print Method conflict with Autoptimize plugin

Home Forums Support Dynamic CSS Print Method conflict with Autoptimize plugin

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #1505204
    Clayton

    Hey guys,

    I’m using Autoptimize to help cache and minify CSS HTML and Javascript. It works well but there does seem to be a conflict. When I have the External File option 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.

    #1505833
    David
    Staff
    Customer Support

    Hi there,

    what doesn’t update ? Changes made in the Customizer ?

    Let me know

    #1505975
    Clayton

    Yes. For example the color of the footer bar or the wrapper width.

    #1506154
    David
    Staff
    Customer Support

    Have you tried clearing the autoptimize cache after making those changes?

    Personally i never develop or customize with a cache plugin enabled as its bound to cause a headache.

    #1506520
    Clayton

    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 conflictingz

    #1506680
    Tom
    Lead Developer
    Lead 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.

    #1506701
    Clayton

    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.

    #1506780
    Clayton

    Figured it out. By default Autoptimize excludes the wp-content/uploads directory 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.

    #1506987
    Tom
    Lead Developer
    Lead Developer

    Ah, thanks for letting us know! Really appreciate it 🙂

    #1569443
    Rylan Urban

    Thanks. I had the same issue. Removing ,wp-content/uploads fixed it.

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