The Interwebs are no help on this one. We're encoding data in ColdFusion using serializeJSON and trying to decode it in PHP using json_decode. Most of the time, this is working fine, but in some cases, json_decode returns NULL. We've looked for the obvious culprits, but serializeJSON seems to be formatting things as expected. What else could be the problem?
Interwebs对此没有帮助。我们使用serializeJSON在ColdFusion中编码数据,并尝试使用json_decode在PHP中对其进行解码。大多数情况下,这工作正常,但在某些情况下,json_decode返回NULL。我们已经找到了明显的罪魁祸首,但是serializeJSON似乎正在按预期格式化。还有什么可能是问题?
UPDATE: A couple of people (wisely) asked me to post the output that is causing the problem. I would, except we just discovered that the result set is all of our data (listing information for 2300+ rental properties for a total of 565,135 ASCII characters)! That could be a problem, though I didn't see anything in the PHP docs about a max size for the string. What would be the limiting factor there? RAM?
更新:一些人(明智地)要求我发布导致问题的输出。我会,除了我们刚刚发现结果集是我们所有的数据(列出2300多个出租物业的信息,总共565,135个ASCII字符)!这可能是个问题,尽管我在PHP文档中没有看到任何关于字符串最大大小的内容。会有什么限制因素?内存?
UPDATE II: It looks like the problem was that a couple of our users had copied and pasted Microsoft Word text with "smart" quotes. Those pesky users...
更新II:看起来问题是我们的几个用户使用“智能”引号复制并粘贴了Microsoft Word文本。那些讨厌的用户......
4 个解决方案
#1
2
You could try operating in UTF-8 and also letting PHP know that fact.
您可以尝试使用UTF-8进行操作,并让PHP知道这一事实。
I had an issue with PHP's json_decode not being able to decode a UTF-8 JSON string (with some "weird" characters other than the curly quotes that you have). My solution was to hint PHP that I was working in UTF-8 mode by inserting a Content-Type meta tag in the HTML page that was doing the submit to the PHP. That way the content type of the submitted data, which is the JSON string, would also be UTF-8:
我有一个问题,PHP的json_decode无法解码UTF-8 JSON字符串(除了你的卷曲引号之外还有一些“怪异”字符)。我的解决方案是通过在HTML页面中插入一个Content-Type元标记来提示PHP,以提示我工作在UTF-8模式。这样,提交数据的内容类型(即JSON字符串)也将是UTF-8:
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
After that, PHP's json_decode was able to properly decode the string.
之后,PHP的json_decode能够正确解码字符串。
#2
1
can you replicate this issue reliably? and if so can you post sample data that returns null? i'm sure you know this, but for informational sake for others stumbling on this who may not, RFC 4627 describes JSON, and it's a common mistake to assume valid javascript is valid JSON. it's better to think of JSON as a subset of javascript.
你能可靠地复制这个问题吗?如果是这样,你可以发布返回null的样本数据吗?我相信你知道这一点,但是为了让其他人磕磕绊绊的信息,RFC 4627描述了JSON,并且认为有效的javascript是有效的JSON是一个常见的错误。最好将JSON视为javascript的一个子集。
in response to the edit:
响应编辑:
i'd suggest checking to make sure your information is being populated in your PHP script (before it's being passed off to json_decode), and also validating that information (especially if you can reliably reproduce the error). you can try an online validator for convenience. based on the very limited information it sounds like perhaps it's timing out and not grabbing all the data? is there a need for such a large dataset?
我建议检查以确保您的信息正在PHP脚本中填充(在它传递给json_decode之前),并验证该信息(特别是如果您可以可靠地重现错误)。为方便起见,您可以尝试使用在线验证器。基于非常有限的信息,它听起来可能是超时而不是抓住所有数据?是否需要这么大的数据集?
#3
1
I had this exact problem and it turns out it was due to ColdFusion putting none printable characters into the JSON packets (these characters did actually exist in our data) but they can't go into JSON.
我有这个确切的问题,事实证明这是由于ColdFusion将没有可打印的字符放入JSON数据包(这些字符确实存在于我们的数据中),但它们不能进入JSON。
Two questions on this site fixed this problem for me, although I went for the PHP solution rather than the ColdFusion solution as I felt it was the more elegant of the two.
这个网站上的两个问题为我解决了这个问题,虽然我选择了PHP解决方案而不是ColdFusion解决方案,因为我觉得这两个问题更优雅。
Fix the string before you pass it to json_decode()
在将字符串传递给json_decode()之前修复它
$string = preg_replace('/[\x00-\x1F\x80-\xFF]/', '', $string);
Use the cleanXmlString() function in that SO question after using serializeJSON()
使用serializeJSON()后在SO问题中使用cleanXmlString()函数
#4
0
You could try parsing it with another parser, and looking for an error -- I know Python's JSON parsers are very high quality. If you have Python installed it's easy enough to run the text through demjson's syntax checker. If it's a very large dataset you can use my library jsonlib -- memory use will be higher than with demjson, but it will run faster because it's written in C.
您可以尝试使用另一个解析器解析它,并查找错误 - 我知道Python的JSON解析器质量非常高。如果您安装了Python,则可以通过demjson的语法检查器轻松运行文本。如果它是一个非常大的数据集,你可以使用我的库jsonlib - 内存使用将高于demjson,但它会运行得更快,因为它是用C语言编写的。
#1
2
You could try operating in UTF-8 and also letting PHP know that fact.
您可以尝试使用UTF-8进行操作,并让PHP知道这一事实。
I had an issue with PHP's json_decode not being able to decode a UTF-8 JSON string (with some "weird" characters other than the curly quotes that you have). My solution was to hint PHP that I was working in UTF-8 mode by inserting a Content-Type meta tag in the HTML page that was doing the submit to the PHP. That way the content type of the submitted data, which is the JSON string, would also be UTF-8:
我有一个问题,PHP的json_decode无法解码UTF-8 JSON字符串(除了你的卷曲引号之外还有一些“怪异”字符)。我的解决方案是通过在HTML页面中插入一个Content-Type元标记来提示PHP,以提示我工作在UTF-8模式。这样,提交数据的内容类型(即JSON字符串)也将是UTF-8:
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
After that, PHP's json_decode was able to properly decode the string.
之后,PHP的json_decode能够正确解码字符串。
#2
1
can you replicate this issue reliably? and if so can you post sample data that returns null? i'm sure you know this, but for informational sake for others stumbling on this who may not, RFC 4627 describes JSON, and it's a common mistake to assume valid javascript is valid JSON. it's better to think of JSON as a subset of javascript.
你能可靠地复制这个问题吗?如果是这样,你可以发布返回null的样本数据吗?我相信你知道这一点,但是为了让其他人磕磕绊绊的信息,RFC 4627描述了JSON,并且认为有效的javascript是有效的JSON是一个常见的错误。最好将JSON视为javascript的一个子集。
in response to the edit:
响应编辑:
i'd suggest checking to make sure your information is being populated in your PHP script (before it's being passed off to json_decode), and also validating that information (especially if you can reliably reproduce the error). you can try an online validator for convenience. based on the very limited information it sounds like perhaps it's timing out and not grabbing all the data? is there a need for such a large dataset?
我建议检查以确保您的信息正在PHP脚本中填充(在它传递给json_decode之前),并验证该信息(特别是如果您可以可靠地重现错误)。为方便起见,您可以尝试使用在线验证器。基于非常有限的信息,它听起来可能是超时而不是抓住所有数据?是否需要这么大的数据集?
#3
1
I had this exact problem and it turns out it was due to ColdFusion putting none printable characters into the JSON packets (these characters did actually exist in our data) but they can't go into JSON.
我有这个确切的问题,事实证明这是由于ColdFusion将没有可打印的字符放入JSON数据包(这些字符确实存在于我们的数据中),但它们不能进入JSON。
Two questions on this site fixed this problem for me, although I went for the PHP solution rather than the ColdFusion solution as I felt it was the more elegant of the two.
这个网站上的两个问题为我解决了这个问题,虽然我选择了PHP解决方案而不是ColdFusion解决方案,因为我觉得这两个问题更优雅。
Fix the string before you pass it to json_decode()
在将字符串传递给json_decode()之前修复它
$string = preg_replace('/[\x00-\x1F\x80-\xFF]/', '', $string);
Use the cleanXmlString() function in that SO question after using serializeJSON()
使用serializeJSON()后在SO问题中使用cleanXmlString()函数
#4
0
You could try parsing it with another parser, and looking for an error -- I know Python's JSON parsers are very high quality. If you have Python installed it's easy enough to run the text through demjson's syntax checker. If it's a very large dataset you can use my library jsonlib -- memory use will be higher than with demjson, but it will run faster because it's written in C.
您可以尝试使用另一个解析器解析它,并查找错误 - 我知道Python的JSON解析器质量非常高。如果您安装了Python,则可以通过demjson的语法检查器轻松运行文本。如果它是一个非常大的数据集,你可以使用我的库jsonlib - 内存使用将高于demjson,但它会运行得更快,因为它是用C语言编写的。