• 88 reviews
Disable Content-Security-Policy
Security impact analysis
0
Manifest
0
Scripts
7
Permissions
0
Hosts

Disable Content-Security-Policy
Disable Content-Security-Policy

Exploring The Best Tools For Web Development: A Comprehensive Review of WordPress Debug Chrome Extension

Discovering efficient tools to expedite your web development process can be a game-changer. With a myriad of utilities available on the Chrome Web Store , finding a reliable browser tool can be quite a task . This article aims to guide you through one such utility, the 'WordPress Debug' chrome extension .

Introduction to WordPress Debug

The WordPress Debug is a top Chrome extension that has accumulated an aggregate rating of 3.59 out of 5, a testament to its functionality and user satisfaction. This utility tool has been lauded for its outstanding features that help developers debug their WordPress websites with ease.

User Reviews: The Good and The Bad

Like any other utility tool, the WordPress Debug chrome extension has received mixed reviews from its users. For instance, Stefanus Diptya, a satisfied user, states, "Works like a charm!". Similarly, PossessWithin praises the extension, saying, "Works perfectly. Thank you very much!"

Despite these positive reviews, other users have indicated some drawbacks that could be improved in future updates. User SpamBox expressed dissatisfaction, saying, "Don't waste your time, it doesn't work at all." Similarly, Vaibhav Nigam pointed out a specific technical issue, stating, "it does not work on a website which adds CSP using HTML meta tag."

Notable Features Of The WordPress Debug Extension

The WordPress Debug extension's ability to disable the Content-Security-Policy header for a tab stands out as a unique feature. This proves especially beneficial when testing new third-party tags and their resource inclusion onto the page. However, this tool should be used as a last resort considering it may disable features designed to protect against cross-site scripting. Therefore, it would be preferable to use report-uri, which instructs the browser to send CSP violations to a URI.

Conclusion

Given the mixed reviews, it's clear that while the WordPress Debug Chrome extension has some compelling features beneficial to web developers, it has some room for improvement. However, with a rating of 3.59 out of 5, it remains one of the top Chrome extensions for WordPress development. It's recommended to give this tool a try and determine if it suits your specific needs.


Disables Content-Security-Policy header for a tab

Helpful in testing third-party tags

Easy to switch on and off

Can be used as a last resort

Facilitates in-depth site inspection

Disabling CSP increases risk of cross-site scripting

Disabling it means losing certain protective features

Overuse can lead to security vulnerabilities

Preferable to use report-uri instead

Disabling CSP may block certain elements

3.62
88 reviews
19 Reviews For This Extension
hailong hu

Very effective

en1ight

29 Jul 2024: its working. For those who messaged its not working: make sure you are using it correctly (you see "blocked:csp" agaist your request in network tab)

Linh Ngọc

Not working for some telegram web bot

Phat Pham

it work like a charm

Colin Brown

Doesn't work

ethan

It works

Jack

awesome

Kostis Anagnostopoulos

Don't bother, it didn't work, at least in Brave Version 1.62.156 Chromium: 121.0.6167.139 (Official Build) (64-bit) From DevTools override headers and delete/modify the response CSP to your liking: https://developer.chrome.com/docs/devtools/overrides

Martin Mudaliar

Worked like a charm!

DEV

did not work locally with iframe logging still this err "Refused to frame 'https://stage.mydomain.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' https://mydomain.com https://*.mydomain.com""

Julián Andrés Núñez

Works fine after refresh

Alex Kubica

Works if you hard refresh ?

SpamBox

Don't waste your time, it doesn't work at all. It had one job to do and it fails miserably at it. Absolutely no change.

Kyle Keating

Still got "Refused to frame" error in Chrome related to the content security policy. Did not work for me.

Brian Coale

Did/changed nothing. All the same CSPs showed up after toggle as were there before, not sure what this is actually for?

Cees Timmerman

I tried other CORS stuff, but this one seems to do Content Security Policies (CSPs) and avoid Cross-Origin Resource Sharing (CORS) errors in Chrome.

Horia Cristescu

There is a small issue - the CSP setting does not remain set. I need to toggle it again and reload the page if I want to see it working. It used to remember its state before.

Stefanus Diptya

works like a charm!

Efecan Yilmaz

Works good

Users count
Rating


Related articles

THIS SITE USES COOKIES

This site, like many others, uses small files called cookies to help us improve and customize your experience. Learn more about how we use cookies in our cookie policy.