-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with WP Rocket lazy loading when content contains an iframe #85
Comments
Hey @jester1979, nice to see you around here. What does the error in your console say? Or do you have a link to where I can see this happening? Thanks! |
En daarna volgt:
|
Thanks, that definitely helps! You're right about the
There should be a slash in front of that Boxzilla uses the default function in WordPress core to dump that object though, |
@dannyvankooten I think I may be seeing weirdness with Gravity Forms ajax mode also. Set up a simple blank site to demo this, go to http://uprecords.org Submit doesn't work, error validation doesn't happen etc. "Doesn't work" is not fully correct actually - network inspector shows the request is made, and correct response is received, but it isn't translated into the box contents. GF ajax works also through a hidden IFRAME. Related? |
I've solved this part. It's about GF attaching its initialization to add_filter( 'boxzilla_box_content', function( $content, $box ) {
$content = str_replace( 'jQuery(document).ready(', 'Boxzilla.on( "done",', $content );
return $content;
}, 12, 2 ); Maybe there's a more general solution to this. I think the original poster's problem is therefore different and your analysis in #85 (comment) seems to solve it correctly - I reached the same conclusion when inspecting the JSON string. |
I have a Box containing an iframe.
When I also use WP Rockets setting for the lazy loading of iframes. My Box doesn't popup anymore.
There is a JS error in my console. ( I think the JSON with the boxzilla params have gotten corrupt somehow )
The text was updated successfully, but these errors were encountered: