doulie0178 2016-08-03 10:08
浏览 351
已采纳

如何修复警告JSON_BIGINT_AS_STRING未实现?

Looking on my Apache error log file, I checked this warning:

PHP Warning:  json_decode(): option JSON_BIGINT_AS_STRING not implemented in /../codebird.php on line 2517

It's referred to a script that I use to auto-post on Twitter from my blog.

This is the guilty function:

  protected function _parseApiReply($reply)
  {
    $need_array = $this->_return_format === CODEBIRD_RETURNFORMAT_ARRAY;
    if ($reply === '[]') {
      switch ($this->_return_format) {
        case CODEBIRD_RETURNFORMAT_ARRAY:
          return [];
        case CODEBIRD_RETURNFORMAT_JSON:
          return '{}';
        case CODEBIRD_RETURNFORMAT_OBJECT:
          return new \stdClass;
      }
    }
    if (! $parsed = json_decode($reply, $need_array, 512, JSON_BIGINT_AS_STRING)) {
      if ($reply) {
        // assume query format
        $reply = explode('&', $reply);
        foreach ($reply as $element) {
          if (stristr($element, '=')) {
            list($key, $value) = explode('=', $element, 2);
            $parsed[$key] = $value;
          } else {
            $parsed['message'] = $element;
          }
        }
      }
      $reply = json_encode($parsed);
    }
    switch ($this->_return_format) {
      case CODEBIRD_RETURNFORMAT_ARRAY:
        return $parsed;
      case CODEBIRD_RETURNFORMAT_JSON:
        return $reply;
      case CODEBIRD_RETURNFORMAT_OBJECT:
        return (object) $parsed;
    }
    return $parsed;
  }
}

Why if the title is too long I'm getting this warning and it doesn't post on Twitter?

P.S.

I have installed PHP 5.5.9 but the problem still the same.

  • 写回答

1条回答 默认 最新

  • dongqi1245 2016-08-03 17:33
    关注

    The JSON_BIGINT_AS_STRING option has only been available since PHP 5.4. You can remove it, but if the numbers contained in your JSON response are too big they will overflow.

    Looking into this further, it appears that there were some problems with JSON's license that have resulted in Debian-based distributions not providing packages for the standard JSON extension. They replace it with a mostly-compatible version that defines a constant JSON_C_VERSION that can be checked for:

    if (defined("JSON_C_VERSION") || version_compare(PHP_VERSION, '5.4.0', '<')) {
        json_decode($reply, $need_array, 512);
    } else {
        json_decode($reply, $need_array, 512, JSON_BIGINT_AS_STRING);
    }
    

    Or, just remove the fourth parameter. I've always used Scientific Linux which is a RHEL distro, so had never come across this issue before.

    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥20 sub地址DHCP问题
  • ¥15 delta降尺度计算的一些细节,有偿
  • ¥15 Arduino红外遥控代码有问题
  • ¥15 数值计算离散正交多项式
  • ¥30 数值计算均差系数编程
  • ¥15 redis-full-check比较 两个集群的数据出错
  • ¥15 Matlab编程问题
  • ¥15 训练的多模态特征融合模型准确度很低怎么办
  • ¥15 kylin启动报错log4j类冲突
  • ¥15 超声波模块测距控制点灯,灯的闪烁很不稳定,经过调试发现测的距离偏大