• The Autoptimize plugins cache is getting very big, and I managed to track dow the issue to this plugin. Is there anybody else with the same issue? Or has a solution?

    • This topic was modified 7 years, 6 months ago by szabyka21.
Viewing 5 replies - 1 through 5 (of 5 total)
  • you could try excluding the inline JS gravity forms creates (and this plugin changes) from AO JS optimization @szabyka21?

    frank (ao dev)

    Thread Starter szabyka21

    (@szabyka21)

    That was a quick answer, Frank. ??
    I tried what you suggested, but got the jQuery not defined error in console.

    Next, I’ll try to track down the unique strings, as you described here

    (@optimizingmatters)Frank did anybody else came up with the same issue using this plugin( Gravity Forms: Multiple Form Instances)?

    • This reply was modified 7 years, 6 months ago by szabyka21.
    • This reply was modified 7 years, 6 months ago by szabyka21.
    • This reply was modified 7 years, 6 months ago by szabyka21.

    for jquery not defined; excluding js/jquery/jquery.js should fix that one?

    But don’t remember people asking about this plugin no, but I had a quick look at the code and it seems to generate a random ID which will then end up in your HTML as inline JS. When aggregating inline JS, this small difference causes AO to re-minify & re-cache that file, leading to your cache getting too big (and other things).

    Thread Starter szabyka21

    (@szabyka21)

    Yes, excluding jquery fixed that, but then my jquery file became render-blocking. Is there a workaround for this, Frank?

    no easy workaround for that I’m afraid, if you have to exclude inline JS because it busts the cache, but that inline JS requires jquery, then you have to choose between purging the cache regularly (which does not fix those other problems) or to exclude jquery ..

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Is this plugin supported? Autoptimize cache size issue.’ is closed to new replies.