
W3tc + Ajax + Fancybox Conflict
4805
$$
- Posted:
- Proposals: 2
- Remote
- #244429
- Archived
Description
Experience Level: Intermediate
My site has a conflict between 3 things: W3tc + Built-in Ajax Lazy Load-like feature, and a Fancybox2 Plugin.
Basically the built-in Ajax/Lazy Load feature (I think this is the root of my trouble) is causing 3 things to happen:
1. W3tc doesn't cache images on the CDN that are below the fold (ie that load after a lazy load 'break'), as it doesn't seem to be rewriting the urls. Did confirm that the images after the fold are indeed on the CDN (I've tried putting cdnsubdomain.mydomain.com/path/to/image.jpg and it appears OK). Happens in FF, Chrome and Safari.
2. Fancy Box slideshow fails to cycle through to images that are also below the fold. i.e. if a slideshow has 150 images, Fancy Box only loads the first lazy load (9 images), not the entire set of 150 images. Happens in FF, Chrome and Safari.
3. In Chrome, only the first set of lazy loaded images are loaded. Others below the second lazy load 'break' (do not load), whereas they do in Safari. It could be an issue with Chrome's issues handling async calls, and should just be a matter of changing the jQuery slightly to allow this.
Need this fixed in less than 3 days.
Basically the built-in Ajax/Lazy Load feature (I think this is the root of my trouble) is causing 3 things to happen:
1. W3tc doesn't cache images on the CDN that are below the fold (ie that load after a lazy load 'break'), as it doesn't seem to be rewriting the urls. Did confirm that the images after the fold are indeed on the CDN (I've tried putting cdnsubdomain.mydomain.com/path/to/image.jpg and it appears OK). Happens in FF, Chrome and Safari.
2. Fancy Box slideshow fails to cycle through to images that are also below the fold. i.e. if a slideshow has 150 images, Fancy Box only loads the first lazy load (9 images), not the entire set of 150 images. Happens in FF, Chrome and Safari.
3. In Chrome, only the first set of lazy loaded images are loaded. Others below the second lazy load 'break' (do not load), whereas they do in Safari. It could be an issue with Chrome's issues handling async calls, and should just be a matter of changing the jQuery slightly to allow this.
Need this fixed in less than 3 days.
Melissa M.
100% (3)Projects Completed
4
Freelancers worked with
3
Projects awarded
36%
Last project
28 Mar 2014
Mexico
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies