htmlspecialchars error when running query from developers_tool_kit

[mc12345678]

Search was performed with
Look-up in all files Key or Name: qty
All Files Look-ups: All Files - Catalog/Admin
File Type: .php
Case Sensitive: Unchecked

Resulted in:

htmlspecialchars(): Invalid multibyte sequence in argument in shop/admin/developers_tool_kit.php on line 190

with post data:

stdClass Object
(
[configuration_key] => qty
[zv_files] => 1
[zv_filestype] => 1
)

I will say that I have modified the developers_tool_kit.php file to remove the first option of None from the Look-up in all files Key or Name's
All Files Look-ups drop down (Ie., bottom row of screen no longer has a drop down selection of None.)
The modification made only commented out the None option when it is populated to the list.
I assume that I did not do/address something additional downstream/associated with the selection made when the search is performed.

Reason for the change was that I was getting tired of having to select an option from the dropdown other than None, when I am typically okay with receiving results from both sides unless I want to reduce the number of results/focus on a particular side of the code. I did not modify the other three options because I rarely use them. I would also say that I am glad to know that if I was reusing the search window (before timing out) that my last selection would remain as the active choice (and all other selection boxes would have the corresponding position "active". Ie. if searched from option 2 of the list, then option 2 of every list would be the active selection for each of the rows.

What did I miss/incorrectly implement when making this change?

[stevesh]

Here's how I did it:

http://www.zen-cart.com/showthread.p...opers-Tool-Kit

[mc12345678]

Here's how I did it:

http://www.zen-cart.com/showthread.p...opers-Tool-Kit

Yeah, if I'm not mistaken that's what I did as well, but instead of deleting the text, I placed comment statements around it. /* array('id' => '0', 'text' => TEXT_LOOKUP_NONE), */
so that I would not "lose" the statement if for some reason it needed to go back and to help me "remember" why that line is different in the php.

So, I got to thinking about the occurrence. First I thought, well maybe something from my cell phone added an odd character to the query request, so I tried again from a desktop using the same query. An additional error log was generated after returning from the query with results, but this time I had clicked on the Search button. So I tried again from the desktop and this time pressed enter after entering the text (reproducing the action taken on my cell phone).

All cases through the htmlspecialchars() error.

I did just recently upgrade to ZC 1.5.1, though am not sure if I was receiving that error before or not. Is there a high potential for me to have not gotten the upgrade fully integrated to my website? Possibly more applicable to the issue, how would I be able to capture what multibyte sequence was sent?

[DrByte]

how would I be able to capture what multibyte sequence was sent?

Add custom code to the script to log all the contents of the $_POST array, then review the log after you re-trigger the problem.