• Observations:

    • WP-SuperCache does not employ JS/CSS Minification or Combination.
    • Flying Scripts injects a single JS Script into the HTML of a site page.

    Outcome:

    • Flying Scripts cannot be excluded from WP SuperCache because there is no JS Keyword or path belonging to an externally enqueued file which can be used for exclusion.

    Is there a solution for this?

    • I love Flying Scripts.
    • I love WP SuperCache.
    • If I have to choose one, it needs to be caching (WP Supercache).
    • I reeeeeeally do not want to have to choose.

    Is there a fix for this documented conflict / issue?

  • The topic ‘WP Super Cache Conflict With Flying Scripts’ is closed to new replies.