Flying Scripts Conflicts With W3-Total Cache

  • Environment:
    WordPress 6.4.2
    Flying Scripts 1.2.3
    W3-Total Cache 6.4.1
    One Signal 2.4.2
    Chaty 3.1.8

    Background:
    I use Flying Scripts to delay the loading of One Signal, Chaty, & MailPoet Plugins.

    I use W3-Total Cache for caching.

    Issue & Observations:
    With W3-Total Cache deactivated, Flying Scripts successfully delays the loading of the One Signal & Chaty plugins (5 second delay).

    With W3-Total Cache activated, Flying Scripts fails to load One Signal & Chaty plugins.

    This conflict occurs when W3-Total Cache is activated – even if all features are turned off, no configuration – no functions turned on. All caching turned-off (page, object, browser, etc.) and no minification or combination used.

    Resetting W3-Total Cache back to factory defaults provides no change.

    The simple existence of WP-Total Cache appears to be an issue for Flying Scripts. Have you seen this before?

    Is there an existing solution to this?

    You can observe this issue here (Flying Scripts is Activated. W3 Total Cache is Activated, no features on (full factory reset of settings).

Viewing 1 replies (of 1 total)
  • Thread Starter MindCreatesMeaning

    (@xizor)

    I’ve moved my website to WP Super Cache.
    My initial post remains worthy of investigating…

    Further Observations:
    W3 Total Cache (breaks Flying Scripts)
    WP Fastest Cache (breaks Flying Scripts)
    WP Super Cache (works with Flying Scripts)

    Far Future Expiry Plugin (breaks Flying Scripts)

Viewing 1 replies (of 1 total)
  • The topic ‘Flying Scripts Conflicts With W3-Total Cache’ is closed to new replies.