Youtube not being blocked in Cornerstone anymore

Hello,

thanks for your message and I’m sorry for this delayed answer.

Have you tried to prior block the specific Youtube content released from our plugin section “Integrations” -> “Script center” -> “Block a script, iframe or plugin”? Furthermore did you put Youtube in the section “Wizard” -> “Consent” -> “Services” -> “Does your website use third-party services? (Yes)”?

Hi there,
thanks for following this up.

Looking under “Integrations->Services”, “Youtube” is activated, it’s also checked in the wizard under “Consent->Services”.

Going through the wizard again doesn’t seem to help.

I did not set anything via the script center, as Youtube usually works via the “Services” (and did work here until recently).
I just tried to add youtube.com and youtube-nocookie.com to a new rule at the script center(“Block a script, iframe or plugin”, “The blocked content is an iframe”), that didn’t change anything though.

Hello,

thanks for your update.

Could you please send us:
1) A video example in which I can see how you’ve embedded a Youtube video in Cornerstone?
2) A video in which I can see how you prior blocked Youtube from the areas I pointed out in my previous message?

Thanks in advance

I don’t know about video, but here’s a picture of how the Video is embedded in Cornerstone (using Cornerstone’s “Classic Embedded Video”-Element):

Here’s the page’s setup:

Here’s the Setup Wizard (in German, but I guess you can tell where it is):

Here’s “Integrations->Services”:

And finally here’s “Integrations->Script Center”:

Does that help?

Hello,

please put in the script center only “youtube.com” and “youtube-nocookie.com”, then save and delete the website cache?

Are you using a cache plugin? If yes, what’s the name of it?

Have you enabled the “Enable cookie and script blocker” from “Wizard” -> “Finish”?

This doesn’t help either, unfortunately:

We’re only using “Autoptimize”, whose cache I’ve been emptying throughout this process.

Here’s the list of active plugins on the site:

AGCA - Custom Dashboard & Login Page: version: 7.2.5, author: Cusmin
All-In-One Image CAPTCHA Pro: version: 8.10.28, author: WP Image CAPTCHA
Autoptimize: version: 3.1.11, author: Frank Goossens (futtta)
Black Studio TinyMCE Widget: version: 2.7.2, author: Black Studio
Burst Statistics - Privacy-Friendly Analytics for WordPress: version: 1.6.1, author: Burst Statistics B.V.
Classic Widgets: version: 0.3, author: WordPress Contributors
Complianz | GDPR/CCPA Cookie Consent: version: 7.0.5, author: Really Simple Plugins
Contact Form 7: version: 5.9.5, author: Takayuki Miyoshi
Cornerstone: version: 7.4.20, author: Themeco
Disable Comments: version: 2.4.6, author: WPDeveloper
Duplicator Pro: version: 4.5.17.3, author: Duplicator
Email Address Encoder ?: version: 0.3.10, author: Till Krüss
Envira Gallery: version: 1.9.10, author: Envira Gallery Team
EventON: version: 4.1.2, author: AshanJay (latest version: 4.6.4)
EventON - RSVP Events: version: 2.7.8, author: Ashan Jay (latest version: 2.9.12)
Favicon by RealFaviconGenerator: version: 1.3.30, author: Philippe Bernard
MainWP Child: version: 5.0.1.1, author: MainWP
OMGF: version: 5.9.0, author: Daan from Daan.dev
Popup Maker: version: 1.19.0, author: Popup Maker
Redirection: version: 5.4.2, author: John Godley
SEO Optimized Images: version: 2.1, author: priyanshu.mittal
Slider Revolution: version: 6.7.9, author: ThemePunch
Smash Balloon Instagram Feed: version: 6.3.1, author: Smash Balloon
Smush: version: 3.16.4, author: WPMU DEV
X – Custom 404: version: 1.1.1, author: Themeco
X – Email Forms (MailChimp): version: 1.1.2, author: Themeco
X – Google Analytics: version: 1.0.0, author: Themeco
X – Smooth Scroll: version: 1.0.2, author: Themeco
X – White Label: version: 1.3.0, author: Themeco
Yoast Duplicate Post: version: 4.5, author: Enrico Battocchi & Team Yoast
Yoast SEO: version: 22.7, author: Team Yoast

Oh, and yes here’s the last page of the wizard:

Since Autoptimize can create a conflict with our plugin could you please follow this guide? https://complianz.io/configuring-autoptimize-with-complianz/

Hi there,

unfortunately, adding ?ao_noptimize=1, ?ao_noptimize=1&cmplz_safe_mode=1 or ?cmplz_safe_mode=1 to the url doesn’t change anything.

Neither does deactivating Autoptimize temporarily…

Also, due to some other conflict, JS isn’t even being optimized on that site, just CSS:

Thanks for all the information provided.

I’m going to open a task for our dev team and I’ll let you know as soon as I’ll have news about it.

In the meantime thanks for your cooperation.

Dear user,

before opening the task could you please specify the exact name of the WordPress theme you’re using? Could you also send me a screenshot of it?

Huh, that finally pointed me in the right direction, thanks!

Theme is “X” (Child) by Themeco: https://theme.co/x
There was a code active in the child theme’s functions.php, that came from their forum and used to help with Complianz breaking Cornerstone.

Here’s the code:

function cmplz_my_filter_site_needs_cookiewarning( $cookiewarning_required) { if ( function_exists('CS') ) { return false; } } add_filter( 'cmplz_site_needs_cookiewarning', 'cmplz_my_filter_site_needs_cookiewarning' );

And here’s where it’s from: https://theme.co/forum/t/complianz-breaks-cornerstone-quickfix/107533

After removing that snippet, the videos are being blocked again.
Cornerstone is back to being broken once more though, as long as Complianz is active.

Still annoying, but a much better situation than before.
That code seems to have worked for some time, but I can’t say which update broke it.

Hard to say who should fix this, if you’re interested in getting Complianz to work with Cornerstone, I’ll be happy to beta test or something ??

And of course mea culpa, I should have checked the functions.php for possible conflicts.

Since the original issue is solved now, I’ll mark this as resolved.
Thanks for the ace support!

Dear user,

thanks a lot for your complete update.

Could you please send me a screenshot/video about how Cornerstone is “broken” by our plugin? This way I’ll be able to update our task and check with the devs if it’s possible to do something about it

Sure, should I open a new Thread for this?

Here’s a screenshot:

Here’s the Error Message:

Uncaught (in promise) TypeError: can't access property "data", window.csAppConfig is undefined
wye https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
EventListener.handleEvent* https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
app.react18.7.4.20.js:135:8315
wye https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
(Async: EventListener.handleEvent)
https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135
https://[snip]/wp-content/plugins/cornerstone/assets/js/app.react18.7.4.20.js?ver=7.4.20:135

Disabling Complianz makes that go away and Cornerstone loads without a problem

Hello,

thanks for the information.

No need to create another thread, I’ll keep you posted.