Many companies test out widgets on developer servers or on an agency domain prior to installing to the live site, but get concerned about the Content Security Policy notice.
Why does this happen?
Reviews should only be published on the domain associated with the REVIEWS.io account, so due to restrictions in the REVIEWS.io Content Security Policy, when installing the widget on a different domain or local developer server you will receive a notice that looks something like below:
Will this stop the widget from showing?
The short answer is no. The Content Security Policy is [report-only] and has zero impact on the display of the widget and will just pop a notice in the Console with details of the policy breach, but the widget will work fine. It will only report the security exception not enforce it.
The widget is still not showing?
Check out our full widget library here for your installation: https://dash.reviews.co.uk/widgets