Hello,
I would like to know why I can't pick this date: 9/2/2012 (September 2nd 2012)
It seems there's an implicit validation JS which puts 9/1/2012 instead the selected date
It is possible to disable this behavior?
Best regards,Víctor
Hi Victor,
Thank you for posting in the community.
Can you provide some more information as to the version of NetAdvantage which you are using and whether the issue is browser specific ? It would be really helpful to see a small sample illustrating this behavior as it sounds quite unusual.
Hi, thanks for answer !! :)
We're using NetAdvantage 2012.1 on a Visual Studio .NET 2010 ASP.NET (VB) Solution.
We tried the webdatepicker control on a simple webform (we tried with and without updatepanel), and when we selected 9/2/2012 (september 2nd 2012), automatically the control set the date on 9/1/2012. The issue extended to the first sunday of september of each year (we cant pick 9/8/2013)
As simple as you read before, nothing more... :(
We tested the solution both Internet Explorer 8 and Google Chrome v19.0.1084.52 with the same odd result. The website is an Intranet, so we cannot provide you an address to test our sample.
The culture configurated in web.config file is "es-MX", we forced webdatepicker's culture to "es-MX" and the problem still continued.
Do you have a sample page we can try your control and compare settings? We are searching for server settings but without luck :(
Best Regards,Víctor
Hello Victor,
Thank you for your reply and for sharing the solution with the community. Glad that the issues has been resolved.
Please do not hesitate to contact me if any further questions regarding this matter arise.
I FOUND IT!!!
Finally, there was no problem with the control.
It's a Windows Update issue!!!
There is an update called KB2681116, in order to fix a Daylight saving time (DST) update for Chile
http://support.microsoft.com/kb/2681116
Unfortunelly, this update has a bug which produce the odd behaviour in your webdatepicker control. So we uninstall the hotfix KB2681116 and problem solved!!! yayyy!!!
Hello Petar,
It's kind wird!!... anyway, I uploaded this video showing the odd behaviour
http://www.youtube.com/watch?v=H46udGWSaI0&feature=g-upl
I really don't know what's happening with the control.
We were thinking about the .NET Framework... our current version is 4.0
Best regardsVíctor
Thank you for your reply.
Unfortunately I am still having no luck to reproduce the matter even with different culture configurations.
You can find live samples of the WebDatePicker control (using 12.1) and compare settings at:
http://samples.infragistics.com/aspnet/Samples/WebDatePicker/Localization/Localization/Default.aspx?cn=date-picker&sid=25edeee6-0a84-4280-9ae0-e22036ada9d1
Please do not hesitate to contact me if you continue experiencing any issues.