Home>Support>Error console on widget bundle activation?

Error console on widget bundle activation?

By Speedyp, 4 years ago. Last reply by Andrew Misplon, 4 years ago.

Hi – been using and loving page builder for years now.
Just noticed in the ffox web console we get a lot of warning for 1 site. The only thing that seems to trigger them is activating the widgets bundle (even if none of the individual widgets in there are activated).

Hoping you might have an idea why? None of the other sites we have (same generate press theme etc) seem to do this/

Warnings:
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Cookie “SIDCC” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To learn more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite embed
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’report-sample’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “’unsafe-inline’” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 4 years, 2 months ago Speedyp

    Ahh… after much probing, turned out to be an iframe with a google map inside in the footer!
    Odd the warnings disappeared when we deactivated the widgets bundle, but there you go – the strange world of t’internet!
    Feel free to delete this query
    Thanks

  2. 4 years, 2 months ago Andrew Misplon
    Hi, I Work Here

    Hi Speedy

    Thanks for reaching out. We’re glad to hear you found the cause of the issue. Thanks for keeping us updated. Cheers for now :)

Replies on this thread are closed. Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More