No FORCE option

[maxviewup]

Some pages the plugin wont identify the JSON. Maybe a force option would solve this. recived from chrome: Resource interpreted as Document but transferred with MIME type application/json: "http://URL".

[nicole-ashley]

@maxviewup can you post a URL to reproduce the issue?

[andxyz]

I am also getting this issue, perhaps a new chrome update is trying to be clever? example url, http://api.thescore.com/search?q=madrid

I would love a force option to look at a "strange query param", so then I could force it on other peoples apis which might set an incorrect Content-type in the response. For example something that isnt: Content-Type:application/json;charset=utf-8

Maybe I could query my previous example with something extra like: http://api.thescore.com/search?q=madrid&force_json_formatter=1

[maxviewup]

http://api.thescore.com/search?q=madrid is a good example.

In my case, the ghostery plugin is blocking this plugin.

[andxyz]

Hmm, perhaps that is my issue too.

[nicole-ashley]

Hmm, I'm not sure about what Ghostery might be doing to it. However my fork of this extension no longer requires a Content Type of application/json. It works with plain text or HTML pages that are purely JSON as well. https://github.com/nikrolls/json-formatter

[andxyz]

Cool, you are actively working on it, I'll try it out.

I believe my original issue was some sort of ghostery extension conflict in the end.

[rejhgadellaa]

So.. does ghostery have an option that I can tick so json formatter works again? Or do I have to disable ghostery?

[maxviewup]

in my case, only disabling ghostery solves the problem. ghostery has a option to trust the site. but this option still conflicts with the plugin.

[irwansetiawan]

I had the same conflict with ghostery. Disabling "Purple Box" which appends HTML to the DOM enables JSON Formatter to work again.

[bodinsamuel]

omg, I was so sad that the plugin was not working for the last months or so Thanks @maxviewup disabling ghostery is indeed THE solution