jQuery Grid Plugin - jqGrid

good stuff.  is there anything that is not backward compatible from an 3.8.2 API point of view that is worth worrying about ??  things seem to work out of the box without too much trouble.

hi

is this bug fixed? It does not seem so according to code.

http://www.trirand.com/blog/?p.....the-pager/

here is my help-thread with the solution posted by oleg:

http://www.trirand.com/blog/?p.....8;search=1

it is really annoying for firefox users since the whole pagination does not work. it would be very friendly if someone from the dev-team at least gives a statement about this. using multiple identic div id's is also not xhtml compliant and for sure will create further issues in the future too.

if there is no willing to take that into an update we will create a fork with a complete and easy-2-use php class and cross-browser compatibility mainly through fixing this annoying bug.

for users needing help you can pm me for the corrected files for 3.8.2 and 4.0 or you can follow oleg's instruction using eclipse or notepad++ and patch rename the variables with regex.

Hello Tony,

Thanks for information. Much appreciated. Couldn't find any statement/changelog. No - i know i could not make out from reading the code.

Best regards

Hi, I upgraded to the latest version of jqgrid and filtering lists stopped working.

I have a column I defined as follows:

{name: 'Status', index: 'status', width: 100, align: "left", title: false, formatter:GenericStatusFormatter, stype: "select" editoptions: {value :":"+GetResources.GetLiteral ("lblAll ")+"; PreEntry:" + GetResources.GetLiteral (")+";lblPreEntry Entry: "+ GetResources.GetLiteral (")+"; lblEntry Diagnostic:" +GetResources.GetLiteral (lblDiagnostic ") + "Order:" + GetResources.GetLiteral (")+";lblOrder Repair: "+ GetResources.GetLiteral (")+"; lblRepair Verify:" +GetResources.GetLiteral ("Notify ")+"; lblVerify" + GetResources.GetLiteral (")+";lblNotify Closed: "+ GetResources.GetLiteral (")+"; lblClosed Delivered:" +GetResources.GetLiteral (")+"; lblDelivered Canceled: "+ GetResources.GetLiteral("lblCanceled ")+"; Rejected:" + GetResources.GetLiteral (lblRejected ")}}

when I change the value of the combo does not send the value selected in the combo tothe server.

The definition of the grid filter is:

$ ("# myGrid"). jqGrid ('filterToolbar', {defaultSearch: "cn"});

Why has stopped functioning filtering by selecting an option from the combo?

I would also be greatful if you could include some more extensive documentation/examples of the changed search functionality, specifically the custom search.

Thanks

Hello Inara,

jqGrid has shrinkToFit parameter which default value is true. It means if you set width parameter of the grid, the column width will be so chnaged to have the common specified grid width. In the way one can easy aligns the grid with other fields on-screen.

If you define no width parameter for the grid the width value from the colModel will be used to set CSS width of the corresponding column header. Different browsers interpret the value either as inner or as outer width.

Best regards
Oleg

Inara,

the changes in the width calculation of jqGrid 4.0 are bug fixes and not the changes in the grid behavior, so one can not speak about the breaking of the backwards compatibility. You can read more about the bug and it fix here. If you play on the bugs you can easy solve your problem with inserting of the width parameter of jqGrid (see my previous answer). For more understanding you can look at the width property of the column in the priveous version of jqGrid after the grid was displayed. You can see that all the width property of all column was changed (reduced) even if the total grid width is small and should not be really shrinked. This old behavior followed to problems especially in case of the usage column hiding and showing after the first showing of the grid.

Regards
Oleg 

Did posting checkboxes from an edit form change in jqgrid 4.0.  i now see "true:false" being passed as the value in the Querystring no matter if i have it checked yes or now.

has anyone else seen this bug ??