Possible conflict with WP Rocket on CDN rewrite

  • Resolved skillsharejp

    (@skillsharejp)


    5 years, 2 months ago

    When I only use CDN turned on of flying images with WP Rocket with its lazyload for image is turned on, logged in users see images from CDN, but logged out users see images from origin server.

    Clearing cache couldn’t solve the problem.

    I’m not sure if this a problem on your side or WP Rocket, but making sure flying images CDN rewrites gets done before wp rocket generates its cache, you should be able to solve.

    • This topic was modified 5 years, 2 months ago by skillsharejp.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Gijo Varghese

    (@gijo)

    @skillsharejp Flying Images only rewrites src and srcset. However, WP Rocket puts the actual URL in data-lazy-src.

    To fix this we’ve to rewrite data-lazy-src and data-lazy-srcset too. But each lazy loading plugin uses different attributes. For example, some use data-src.

    So it will be hard to fix since there are too many possibilities. I would suggest using the Flying Images’ lazy load instead.

    Plugin Author Gijo Varghese

    (@gijo)

    @skillsharejp this has been fixed in v2.4.1

    Thread Starter skillsharejp

    (@skillsharejp)

    Hi Gijo,

    I’ve updated to the latest version of flying images, but with wp rocket’s lazyload for img is on, images are not delivered from cdn.

    When I disable lazyload for img on wp rocket, images are then delivered from statically cdn.

    Could you double check if this is fixed in 2.4.1?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Possible conflict with WP Rocket on CDN rewrite’ is closed to new replies.

Tags