Hi @rmeegs98dh,
Sorry to hear you’re having trouble! I’d be happy to work with you to try to get this resolved.
Would it be possible for you to temporarily disable all plugins except Wicked Folders on the instance that is having the issue and confirm if the issue persists?
Thank you for the reply.
Initially I’d rather not disable all plugins because like I said, this is only affecting my live site. And, naturally I want to keep my live site working!
I’m no expert, but do you think this could be to do with the security headers I have added for my site (in the apache/nginx config)?
Because I can see some wickedfolder script is blocked, by looking in our web console (the output is in my first post).
Maybe the setting I have set it to is too strict?
Thanks
-
This reply was modified 7 years, 6 months ago by
rmeegs98dh.
No problem, that makes sense.
Yes, I believe it is being caused by the content security policy; however, if I understand the error correctly, I think it is actually being caused by a script that is being loaded via load-scripts.php (if you view the page source and search for “load-scripts.php” you can see which scripts are loaded).
The folder panel depends on several scripts that are bundled with WordPress including jQuery, Backbone and some jQueryUI scripts. My guess is that one of those scripts is being blocked by the security policy which is preventing the folder panel from loading. If I’m not mistaken, jQuery uses the eval() function which might be triggering it to get blocked by the policy.
Do you have issues with any other JavaScript functionality on the live site (such as with the media modal)?
At the moment, it seems like the security policy would need to be tweaked to allow whichever script(s) is being blocked in load-scripts.php in order to get it working.
Let me know if I’m misunderstanding anything or if you have any additional error messages that may help troubleshoot the issue.
Hi @rmeegs98dh,
Just wanted to follow up on this. Did you have any luck narrowing down which script was being blocked by the content security policy?
Let me know if I help with anything.
Hi, thank you for giving me more information about what needs eval() – I removed the ‘too stict’ line for the CSP header and now the folder panel is showing up perfectly.
Now I need to work out the strictest CSP header setting I can use without breaking anything – but that’s my problem!
Thank you for the help, it’s all sorted now 🙂
Great, thanks @rmeegs98dh!