the popular cookie plugin Borlabs does not recognize the Cwicly Video Block while the WordPress Video Block works fine. I think I’m not the only one using this plugin, would be great if you can modify your code so that Borlabs blocks the content.
I contacted the support from Borlabs for information about their discovery process. They told me the following:
The iframe needs to be inside the “the_content() hook”. If that’s the case Borlabs blocks the content automatically. If the iframe is generated by the browser via JavaScript, Borlabs can’t find the iframe.
The Cwicly video block does return an iFrame inside the 'the_content' hook. Might be something they’re missing after-all.
I’ll also have you note that we do provide an in-built privacy protection feature with the Div Overlay property (no communication with YouTube until the Div is clicked) + no-cookie YouTube.
that’s interesting. Didn’t realize this was passible – very nice!
But still in some cases I would like to use Borlabs because the user just needs to accept the conditions once. I will contact Borlabs again hopefully they will take a look.
Borlabs blocks the Cwicly Video Block as long as it is no used in templates.
When I create a Post Template with a Video Block that uses the URL from an ACF on the post page Borlabs does not find the Video Block. Shen I put the Video Block inside the Post Content Borlabs works fine.
So it seems that there is indeed an issue with Cwicly. Could you maybe take a look if that is something you can fix? I can send you a copy of the Borlabs Plugin for testing.
Yes, that’s correct. Just some minor styling issues because the Borlabs block that replaces the iframe is not set to absolute and thereby pushed out of the frame.
Video #1 is the Cwicly Block inside the index template.
Video #2 is the Gutenberg Video Block inside the post content.
Video #3 is the Cwicly Video Block inside the post content (the video block is the white rectangle. if you inspect it you see that the video is just pushed out because of the padding).
Video #4 is the Gutenberg Video Block inside the index template.
as I am facing the same issues like @Jonas, I was wondering if it is possible to work with the shortcodes being provided by borlabs for the case the content is not blocked.
Here’s a sample for the youtube block shortcode: [borlabs-cookie id=“youtube” type=“content-blocker”]URL[/borlabs-cookie]
Here’s the source of information: How to block YouTube & Vimeo videos
Returning here a bit late since I forgot to get back to you once I had checked this out.
I’ve tried with multiple Gutenberg plugins on the Site Editor and it seems Borlabs doesn’t filter them either, so not sure why you are inclined to think there is an issue with Cwicly specifically here.
I suggest you get in touch with Borlabs support and ask them why the core block is the only filtered one when used inside an FSE template.
Once again, the Cwicly Video block renders <iframe> tags directly.
I recorded a short video to explain exactly what the issue is for me. It would be great if you could take a look and let me know what you think about this.
Thank you for the video, but as said in my previous, Borlabs is having trouble parsing videos that are not part of Core when used on the Site Editor. I tried this with different FSE themes and various plugins, and they seem to only block the core/video block when used in FSE/Site Editor/Template.
If they are able to confirm that the issue is coming from our side for one reason or another (although once again, I can repeat this issue with other plugins and Cwicly deactivated), then we’ll definitely fix it.
I’m now facing this same issue. I can work around it but this made me wonder, is there a way that cwicly could implement showing youtube videos directly from the server? like with google fonts? I know for example smashing baloon plugin does that with social media posts, generate a local copy to avoid loading any third party cookies at all. Although maybe it’s not practical due to video weight? Maybe a way to store the consent info when people click the video to be fully compliant with GDPR it would make the privacy setting unmatched and I would be able to get rid of borlabs once and for all
I’m sure this is not practical due to resources needed. I contacted the support of Borlabs about this and they told me they will try to fix this with version 3.0. I provided them a copy of Cwicly but it seems they did not activate it yet meaning they did not start working on it unfortunately.
I think it would be great if you also would contact the Borlabs support about this issue so they know I’m not the only one who needs this fixed.
Initially they planed to release 3.0 in September.
I like the idea of GDPR features integrated into cwicly a lot!
Your idea of saving a YT-video on the server goes way too far imho. But a lean and elegantly working compromise could be to download the preview Picture from YT and offer a link to open in a new tab. Below that a simple cookie based solution to unlock this or all YT content. Basically what Borlabs Cookie plugin offers, just integrated.