I have a webdropdown that has the selected value of < ALL Agents >. After postback the value is converted to %3C%20ALL%20Agents%20%3E. This issue cropped up after upgrading from 14.2 to 15.1. Any help is appreciated.
Thank you,
Hello,
Thank you for posting in our community!
This issue was introduced with the latest Service Release. For 15.1 ASP.NET product the Service Release version is 15.1.20151.2278
This behavior is logged in our internal tracking system with a Development ID of 207719 “After postback the space is encoded as %20 and it is displayed as %20 in the input”.
You can view the status of all development issues connected to this case from the "Development Issues" tab, when viewing this case on the "My Support Requests" page of our website.
We are currently working on resolving this issue. I suggest you to use a previous version of the product until an official fix is released. Please note, the volume release version for 15.1 (prior to .2278) is available for download vial our website at https://es.infragistics.com/my-account/keys-and-downloads/
I have the same problem with version 15.2. Any fix for this?
Seriously, you introduce a significant visual bug from 20142.2480 to 20142.2580 and tell us "upgrade to 2015 or to bad"? That is a horrible answer. I don't have authority to tell my organization shell out the $$$ for upgrade for all our licenses. If I tell them they have to "buy the fix" they will tell me to re-write the application and dump Infragistics. I'm one of a few handfuls of developers that HAVE NOT re-written and moved to other solutions. I suggest fixing this in 20142! I work for Citi.
This REALLY makes me mad! This bug was introduced in the "LAST SR" for 2014.2. I'm currently in the process of DOWNGRADING to SR 2480. Maybe I just tell my management we should stop using Infragistics and take a DEV Cycle to re-write in one of the other options we have available. They have been bugging me about it for 2 years...maybe they get their wish.
Hello All,
After further looking into this matter, it appears the issue is affecting many of our customers. In order to improve the user experience, we decided to make an exception in this case and release additional Service Release for 14.2 containing the fix as well. I will further let you know when such is created and available to the public.
I just want to let you know the patch including this fix is already available for download on our website - https://es.infragistics.com/my-account/keys-and-downloads/
What is more, the Platform Installer is also updated so it downloads the latest patch as well –14.2.20142.2590
After applying 2590, every dropdown in my application now throws an ASP.NET exception during selection changed prior to the postback hitting the server.
Exception information:
Exception type: ArgumentNullException
Exception message: Value cannot be null.
Parameter name: stringToUnescape
at System.Uri.UnescapeDataString(String stringToUnescape)
at Infragistics.Web.UI.ListControls.WebDropDown.LoadControlState(Object savedState)
at System.Web.UI.Control.LoadControlStateInternal(Object savedStateObj)
at System.Web.UI.Page.LoadAllState()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Attached is an sample project showing the issue if more than 1 dropdown is on the page. If only 1 dropdown exists there is no issue.
All my WebDropDown are outside of grids : only inside a WebGroupBox. I was able to determine a valid "Replace All" option and updated 397 dropdowns ... yeah a dropdown buffet! The application is now working as expected. I still might wait for my 2015 license to be purchased and skip the SR, but at least I have an option to deploy it now. A bit of a pain, but a feasible workaround for my application.
This workaround is not working for WebDropDowns in WebDatagrid template columns! Please fix ist asap in V14.2
So the last 2 SRs introduced a bug in WebDropDown...no comment.
Sure I can work around that...update ~70 ASPX files to set a current value attribute on >200 WebDropDowns.
I'll get right on that one...or wait until my company finally acquires the 2015 licenses and leapfrog the buggy SRs!
Thank you for noticing this!
It is indeed introduced in the latest 2590 SR. After further investigating the issue, it could be reproduced only when having an empty WebDropDown on the page and it is more like an edge case. As a workaround I could suggest you to make sure having a set value at all times if applicable. It could contain empty string as a value. For example:
<ig:WebDropDown ID="WebDropDown2" runat="server" Width="200px" CurrentValue=""></ig:WebDropDown>