Thanks for your responses

Yes it appears that unsafe-inline scripts are required for WordPress itself to work, tried a fresh install of WordPress with both the classic editor and Gutenberg and both fail to load the page builders, unfortunately our info-security team won’t allow the site to have these “unsafe-inline” elements due to the security risks.

I have managed to work around the issue by declaring a hash (sha256-XYZ) for each of the inline scripts that are required for the front end to work and repeating all of the inline styling that the theme uses in the child theme CSS file.

While this works for the front end, WordPress and the Enfold Theme builder use far too many inline scripts to declare each of them for the back end (think I counted around 90 on one page), luckily we have hosting with a staging environment so I am currently running the staging environment with the Content Security Policy commented out in the .htaccess file, so the site is usable and the backend can be accessed and all edits made to this environment, then when I deploy to live I activate the security policy so that the public facing site is secure and free of unsafe-inline scripts and styles.

OK so I have found the culprit! The WP Super Cache plugin was causing the issues. Now deactivated. All is once again harmonious in the chaotic world of website development!

Hi Vinay,

Thanks for getting back to me so quick.

I have followed your instructions and executed a hard refresh.

Unfortunately the issues prevail.

Which type of login details do you require? Access to the server via FTP or WordPress Admin?

Darrell