Hi,
we had an issue that the filter menu of the a infragistics grid (both igHierarchicalGrid and igGrid) does not hide by upgrading our jQuery from 1.6.2 to 1.7.1 according to your recommendation. here is the complete thread. http://ko.infragistics.com/community/forums/t/79637.aspx
recently we got a problem that when the datasource contains the character pound key (#) somewhere in the text then the igHierarchicalGrid will not load.
to be more accurate, it doesn't happen all the time, from my testings it happens if the record that contains the # is the first record.
after continues troubleshooting we have detected that this is caused by our upgrade of jquery 1.6.2 to 1.7.1. which we had doubt of how our entire solution will perform if we upgrade , all seemd to be ok but this specific problem.
i've prepared a sample project that demonstrates this issue https://app.box.com/files/0/f/1221162121/1/f_10909570415
at index.aspx uncomment <script src="../../Scripts/jquery-1.7.1.min.js" type="text/javascript"> and comment <script src="../../Scripts/jquery.min-1.6.2.js" type="text/javascript"></script>in order to see the problem
the error you will see in the chrome debuger is Uncaught Error: Syntax error, unrecognized expression: "123"
please help
anyone?
Hi, Thank you for your response and you sample project however can you please look at mine
I've placed the sample project in google drive , please try to download it from there.
https://drive.google.com/file/d/0B_wjtlkijYV6anFzNlhXd2V2VGc/edit?usp=sharing
after you get to the link page click on the "File" in the menu bar and then select "Download" at the bottom of the dropdown menu.
can you please take a look.
Thank you again for your reply.
Peter ?
Hello sharik,
Thank you for your replies.
Please note that the loader and combined Ignite UI scripts should not be referenced at the same time as conflicts are possible. In the context of the provided sample removing the loader reference should ensure that there are no issues in that respect.
After investigating the matter further, it appears that this was an existing behavior in the RTM for volume 12.2 which is used in the sample which has since been fixed. Upgrading to the latest SR for 12.2 or a newer product version should therefore resolve the matter. For reference, you can test the scenario with the latest SR from the CDN:
<link rel="stylesheet" type="text/css" href="../../Infragistics/Style/IG/css/structure/infragistics.css" />
<link rel="stylesheet" type="text/css" href="../../Infragistics/Style/IG/css/themes/metro/infragistics.theme.css" />
<script src="../../Scripts/jquery-1.7.1.min.js" type="text/javascript"></script> <%-- <== causing error--%>
<script src="../../Scripts/jquery-ui.min.js-1.8.23.js" type="text/javascript"></script>
<%-- <script src="../../Infragistics/Script/IG/js/infragistics.loader.js" type="text/javascript"></script>--%>
<script src="http://cdn-na.infragistics.com/jquery/20122/latest/js/infragistics.js" type="text/javascript"></script>
thank you for your reply and solution !!, i will check this.
Thank you for your reply. Please do not hesitate to contact me if any issues arise.