#47130 [Bgs]: JSON problems

ID: 47130 Updated by: scottmac@php.net Reported By: svacinap at compsys dot cz Status: Bogus Bug Type: JSON related Operating System: Linux Slackware 12.1 PHP Version: 5.2.8 New Comment: The fact that it worked before was the bug. It's now doing what it should have done in the first place. Previous Comments: ------------------------------------------------------------------------ [2009-01-19 21:24:06] svacinap at compsys dot cz I meant: So Groupoffice3 developer says: "This is php bug" ------------------------------------------------------------------------ [2009-01-19 21:17:38] svacinap at compsys dot cz OK. Group-office is the php web aplication .. I am IT administrator of the linux systems, NOT a programmer (my fault) ... OK. If I have Groupoffice3 and php 5.2.6 on my server, I can read the email messages, no problem, no errors : http://www.gmork.cz/files/oldphpworks.png OK. If I have updated php to recent version 5.2.8, some of messages which have been made in the php aplication Groupoffice3 CAN NOT be read: http://www.gmork.cz/files/test-again.png So php developer says: "This is php bug" , so php developers says "This is not bug". OKI. Sorry I don't know what to think, because I am not goddam programmer at all ... :-( ------------------------------------------------------------------------ [2009-01-19 16:00:41] scottmac@php.net It didn't work before, it just silently cut the string in half and you never noticed it. See bug #43941 ------------------------------------------------------------------------ [2009-01-19 13:54:39] svacinap at compsys dot cz OK, but there were no problems with json_encode (the same script) in the php version 5.2.5 and 5.2.6 .. So I don't understant what is wrong. Here you have whole script: http://www.gmork.cz/files/json.php.txt ------------------------------------------------------------------------ [2009-01-18 15:37:37] scottmac@php.net Any strings passed to json_encode should be valid utf-8, the manual and error message make this clear. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/47130 -- Edit this bug report at http://bugs.php.net/?id=47130&edit=1