Question

我有一只json_encoded阵列,罚款。

我需要从一项职能呼吁中取消对出租车的所有钥匙的双重引用。

我将如何做到这一点,并成功返回?

感谢!

I do apologise, here is a snippet of the json code:

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

Just to add a little more info:

我将听取日本宇宙航空研究开发机构的请求,这样,如果会比较容易的话,我可以就如何在javascript一侧这样做发表意见。

Answer 1

EDITED as per anubhava s 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;

这无疑有助于上述努力,尽管也许有一些近似的事例,我认为这些案例不会奏效。这是否适合您的目的,取决于说明的形式和内容/价值如何固定。

Answer 2

TL;DR: Missing quotes is how Chrome shows it is a JSON object instead of a string. Ensure that you have Header( Content-Type: application/json; charset=UTF8 ); in PHP s AJAX response to solve the real problem.

DETAILS: A common reason for wanting to solve this problem is due to finding this difference while debugging the processing of returned AJAX data.

In my case I saw the difference using Chrome s debugging tools. When connected to the legacy system, upon success, Chrome showed that there were no quotes shown around keys in the response according to the debugger. This allowed the object to be immediately treated as an object without using a JSON.parse() call. Debugging my new AJAX destination, there were quotes shown in the response and variable was a string and not an object.
I finally realized the true issue when I tested the AJAX response externally saw the legacy system actually DID have quotes around the keys. This was not what the Chrome dev tools showed. The only difference was that on the legacy system there was a header specifying the content type. I added this to the new (WordPress) system and the calls were now fully compatible with the original script and the success function could handle the response as an object without any parsing required. Now I can switch between the legacy and new system without any changes except the destination URL.

友情链接