Here's a weird phenomenon.
Everything was working fine with our RadTabStrip until upgrading to the latest Telerik version.
We have a tab strip where new pageViews are being created dynamically.
In one pageView we have a few RadDateInputs among other input fields.
Upon completion, you click a submit button that takes you to the next tab (a page with RadGrid where you can manage attachments - edit, delete and add files).
If you wishes to go back and correct your input you may click the earlier tab and edit your input.
This was running with no problem before the upgrade.
Now, the first submission goes without a hitch. However, if one goes back and re-submit, we get this error:
Anyone has encountered such problems after upgrade.
We've been going wild over this problem for two whole days now, trying to figure out where the problem is...
If there's a problem with the date format, how does it go through the first time?
Many thanks for any clue.
Everything was working fine with our RadTabStrip until upgrading to the latest Telerik version.
We have a tab strip where new pageViews are being created dynamically.
In one pageView we have a few RadDateInputs among other input fields.
Upon completion, you click a submit button that takes you to the next tab (a page with RadGrid where you can manage attachments - edit, delete and add files).
If you wishes to go back and correct your input you may click the earlier tab and edit your input.
This was running with no problem before the upgrade.
Now, the first submission goes without a hitch. However, if one goes back and re-submit, we get this error:
Text property cannot be set. String was not recognized as a valid DateTime. |
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. |
Exception Details: System.InvalidCastException: Text property cannot be set. String was not recognized as a valid DateTime. |
Source Error: |
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace: |
[InvalidCastException: Text property cannot be set. String was not recognized as a valid DateTime.] |
Telerik.Web.UI.RadDateInput.RangeTextProperty(String value) +192 |
Telerik.Web.UI.RadDateInput.set_Text(String value) +22 |
Telerik.Web.UI.RadInputControl.LoadPostData(String postDataKey, NameValueCollection postCollection) +103 |
Telerik.Web.UI.RadDateInput.LoadPostData(String postDataKey, NameValueCollection postCollection) +26 |
Telerik.Web.UI.RadWebControl.System.Web.UI.IPostBackDataHandler.LoadPostData(String postDataKey, NameValueCollection postCollection) +13 |
System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) +346 |
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1743 |
-------------------------------------------------------------------------------- |
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082 |
Anyone has encountered such problems after upgrade.
We've been going wild over this problem for two whole days now, trying to figure out where the problem is...
If there's a problem with the date format, how does it go through the first time?
Many thanks for any clue.