muttleydosomething

??

Thanks for the reply, after looking further into it I’ve come to understand there are many issues people are experiencing using IIS as a server so I’ve zapped that one and gone with Apache 2.

Since then there are no issues.

Thanks for your time

.

That was a weird one. It turned out to be my browser. I cleared out all of today’s history logins – everything.

When WordPress was accessing my site it was for some reason adding :8080 after the url and then not connecting.

Strange.

Thanks for your help Jose. ??

That’s an idea, will give it a go and take a look

*SOLVED*

I disabled the plugin WPFORMS Lite and charts appeared straight away.

??

I have found that my problem was caused by my Web Server (IIS 10) In the HTTP Response Headers. Having Content-Security-Policy script-src ‘self’ was limiting the scripts that could run stopping the use of many plugins, including WordPress itself from working.

Content-Security-Policy is worth looking further into!

Thanks to t-p for pointing me in the right direction

Thank you t-p for your terrific suggestion.
Adding define(‘SCRIPT_DEBUG’, true); to wp-config.php helped Chrome find the following problem with JavaScript:

Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘self'”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-/YpbaZxLCFpfmU+h0cXYjk1fkxdbHfO5UXAKf7NKes8=’), or a nonce (‘nonce-…’) is required to enable inline execution.

Along with many others…

/wp-admin/plugins.php line 7 etc…

There seems to be a problem with anything that even mentions
<script type=”text/javascript”> etc…

Is there a simple way you know of to fix this? Thanks again!

• This reply was modified 3 years, 11 months ago by muttleydosomething.