• Resolved alx359

    (@alx359)


    Flying Images seems incompatible with WP Fastest Cache. When I turn WPFC On, the cdn.statically.io prefix stops appearing in the image tags. Other similar to FI services (e.g. OptiMole) work fine in conjunction with WPFC, and also with WPFC’s Cloudflare integration. Any way to fix this? Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Gijo Varghese

    (@gijo)

    @alx359 Flying Images will not be compatible with W3TC due to the way it outputs HTML. I would suggest using some other cache plugin

    Thread Starter alx359

    (@alx359)

    Flying Images will not be compatible with W3TC

    Ok, but the posted question meant WPFC (WP Fastest Cache). Suppose is just a typo, but would please still confirm this? Thanks.

    Plugin Author Gijo Varghese

    (@gijo)

    @alx359 Sorry for the typo. I haven’t tested with WP Fastest Cache. It should work

    Thread Starter alx359

    (@alx359)

    Ah, ok, but then it didn’t when I tested. Please see first post.

    Plugin Author Gijo Varghese

    (@gijo)

    @alx359 will test it out once I’ve some free time

    Thread Starter alx359

    (@alx359)

    I’m also confused about W3TC (W3 Total Cache).

    In the post above you said:

    Flying Images will not be compatible with W3TC due to the way it outputs HTML. I would suggest using some other cache plugin

    But in the changelog for v.2.4.6:

    2.4.6
    [NEW] Support for W3 Total Cache

    What gives?

    EDIT: Whatever. W3TC looks too complex and overwhelming anyway. What other cache plugins (apart of WP-Rocket. Preferably free/mium) would you recommend to work well with FI? Hope you could have a look and fix the compatibility issue with WP Fastest Cache in the not so far future. Thanks.

    Thread Starter alx359

    (@alx359)

    As have digged into another compatibility issue for WPFC before, decided to have a look into this one too. It seems fixed now by following the same bridge approach like in w3tc:

    1) NEW file wfpc-bridge.php copied into plugins\nazy-load\lib containing the following code:

    // Check WFPC is active
    if (
        !in_array('wp-fastest-cache/wpFastestCache.php', get_option('active_plugins'))
        && !(is_multisite() && in_array('wp-fastest-cache/wpFastestCache.php', get_site_option( 'active_sitewide_plugins')))
    ) {
        return;
    }
    
    function flying_images_wfpc_bridge() {
        // TODO: Check WFPC lazyload is active and may do something about it
        if( isset( $GLOBALS["wp_fastest_cache_options"]->wpFastestCacheLazyLoad ) ) {
            //return;
        }
    
        add_filter('flying_images_output_buffer', '__return_false', 10);
    
        // Handle buffer before plugin starts work
        add_filter('wpfc_buffer_callback_filter', function( $buffer, $extension ) {
            if( $extension == 'html' || $extension == 'mobile' ) {
                   return flying_images_rewrite_html( $buffer );
            } else return $buffer;
        }, 10, 2);
    }
    
    add_action('plugins_loaded', 'flying_images_wfpc_bridge');

    2) At plugins\nazy-load\html-rewrite.php add below line 3:

    include('lib/w3tc-bridge.php');
    include('lib/wfpc-bridge.php'); #<--
    Plugin Author Gijo Varghese

    (@gijo)

    @alx359 Great! I’ll update soon

    Plugin Author Gijo Varghese

    (@gijo)

    @alx359 released v2.4.9!

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Incompatibility with WP Fastest Cache’ is closed to new replies.