Remove double quotes from json_encoded string on keys

Question

I have a json_encoded array that is good.

I need to strip double quotes on all the keys of a json string by returning them from a function call.

How can I do this and successfully return?

Thanks!

Sorry, here is the json code snippet:

{"start_date":"2011-01-01 09:00","end_date":"2011-01-01 10:00","text":"test"} 

Just add a little more info:

I will receive JSON through an AJAX request, so if it is easier, I am open to ideas on how to do this on the javascript side.

Answer 1

EDITED according to anubhava comment

 $str = '{"start_date":"2011-01-01 09:00","end_date":"2011-01-01 10:00","text":"test"}'; $str = preg_replace('/"([^"]+)"\s*:\s*/', '$1:', $str); echo $str; 

This certainly works for the above line, although there may be some extreme cases that I didn’t think of, for which this would not work. Whether this will meet your goals depends on how static the format of the string and the elements / values ​​contained in it will be.

Answer 2

TL DR: missing quotes is how Chrome shows that it is a JSON object, not a string. Make sure you have a header ('Content-Type: application / json; charset = UTF8'); in PHP, AJAX answer to solve a real problem.

DETAILS. A common reason for wanting to solve this problem is to detect this difference when debugging the processing of returned AJAX data.

In my case, I saw the difference using the Chrome debugging tools. When successfully connecting to an outdated system, Chrome showed that no quotes around the keys in the response were shown in the debugger response. This allowed the object to be immediately processed as an object without using the JSON.parse () call. When debugging my new AJAX assignment, quotes were shown in the response, and the variable was a string, not an object.
I finally realized the true problem when I tested the AJAX answer when I saw that the legacy system actually contained quotation marks around the keys. This was not what the Chrome Developer Tools showed. The only difference was that in the old system there was a header indicating the type of content. I added this to the new system (WordPress), and now the calls were fully compatible with the original script, and the success function could process the response as an object without any analysis. Now I can switch between the obsolete and the new system without any changes except the destination URL.