Hi Rouslan,
I'm trying to debug a case where clicking on SQL does not bring the SQL panel. Firebug shows me that the call to db_sql.php returns a null value in message.
I found how to trigger this behavior: having a public bookmark whose label contains a character like "é". This server runs PHP 5.3.25.
I think it happens because json_encode() is not happy with the content. I have read on http://php.net/json_encode that this function expects string data to be UTF-8 encoded.
I have tried to use utf8_encode() on the results of $this->_getDisplay() before assigning it to $this->_JSON['message'] but it produces mangled HTML on my SQL page.
Any hint?
Marc Delisle a écrit :
Hi Rouslan,
I'm trying to debug a case where clicking on SQL does not bring the SQL panel. Firebug shows me that the call to db_sql.php returns a null value in message.
I found how to trigger this behavior: having a public bookmark whose label contains a character like "é". This server runs PHP 5.3.25.
I think it happens because json_encode() is not happy with the content. I have read on http://php.net/json_encode that this function expects string data to be UTF-8 encoded.
I have tried to use utf8_encode() on the results of $this->_getDisplay() before assigning it to $this->_JSON['message'] but it produces mangled HTML on my SQL page.
Any hint?
It might be because my PMA__bookmark table contains old bookmarks which, in a prior version, stored these accented characters as is in the label. I tried creating a bookmark and with the current version, the label contains the equivalent encoded character.
On 9 Dec 2013, at 21:03, Marc Delisle marc@infomarc.info wrote:
Marc Delisle a écrit :
Hi Rouslan,
I'm trying to debug a case where clicking on SQL does not bring the SQL panel. Firebug shows me that the call to db_sql.php returns a null value in message.
I found how to trigger this behavior: having a public bookmark whose label contains a character like "é". This server runs PHP 5.3.25.
I think it happens because json_encode() is not happy with the content. I have read on http://php.net/json_encode that this function expects string data to be UTF-8 encoded.
I have tried to use utf8_encode() on the results of $this->_getDisplay() before assigning it to $this->_JSON['message'] but it produces mangled HTML on my SQL page.
Any hint?
It might be because my PMA__bookmark table contains old bookmarks which, in a prior version, stored these accented characters as is in the label. I tried creating a bookmark and with the current version, the label contains the equivalent encoded character.
So, I guess this is a non-issue.
-- Marc Delisle http://infomarc.info | http://phpmyadmin.net
Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.cl... _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Le 2013-12-10 05:23, Rouslan Placella a écrit :
On 9 Dec 2013, at 21:03, Marc Delisle marc@infomarc.info wrote:
Marc Delisle a écrit :
Hi Rouslan,
I'm trying to debug a case where clicking on SQL does not bring the SQL panel. Firebug shows me that the call to db_sql.php returns a null value in message.
I found how to trigger this behavior: having a public bookmark whose label contains a character like "é". This server runs PHP 5.3.25.
I think it happens because json_encode() is not happy with the content. I have read on http://php.net/json_encode that this function expects string data to be UTF-8 encoded.
I have tried to use utf8_encode() on the results of $this->_getDisplay() before assigning it to $this->_JSON['message'] but it produces mangled HTML on my SQL page.
Any hint?
It might be because my PMA__bookmark table contains old bookmarks which, in a prior version, stored these accented characters as is in the label. I tried creating a bookmark and with the current version, the label contains the equivalent encoded character.
So, I guess this is a non-issue.
Well, I'm probably not the only user with bookmarks created in an older version and containing such characters. You think that a FAQ entry explaining this would suffice?
-
Marc Delisle -
Rouslan Placella