If you want modify the code you should better use $.jgrid.jqID instead of replacement of blanks to undescores. The function $.jgrid.jqID are used in the most places of jqGrid code, but still not everywhere. The problem it very easy. It one have meta-characters as the part of id and one want to use the id as a part of the jQuery selector one have to escape the characters. The method $.jgrid.jqID do exactly the job.

Regards
Oleg

It's important feature and not a bug. The defaultSearch option of filterToolbar method set default options for all columns. It makes problems. Let us you have colum with select having “equal” and “not equal” option. If you would use defaultSearch:'cn'

You should use really the latest version of jqGrid which are 4.3.1 now. Moreover you should use jquery.jqGrid.src.js instead of jquery.jqGrid.min.js if you post an error. You should also always write which web browser you used in your tests. The best would be if you post a small demo which can be used to reproduce the problem. Could you post additional information?

Best regards
Oleg

I think that the origin of the described bug is the line 1542:

postdata = postdata.split(",");
which modifys the postdata. The postdata variable will be used later not only the the line

Hello,

I just answer on your question here. I think that the problem is the mix of the wrong usage of inlineNav parameters and the bug in the code of “Save” button.

Best regards
Oleg

P.S. I hope that Tony will read the post and will fix the code of

Hello Tony,

I know that

Inside of both addRow

$($t).jqGrid('addRowData', p.rowID, p.initdata, p.position);
(see here) and editGridRow
$($t).jqGrid("addRowData",ret[2],postdata,p.addedrow);

(see here) call addRowData with tree parameter, so it is impossible to use 'after' and 'before'