My two RadSchedulers work perfectly on my developer machine within Visual Studio. When I deploy to the production web server, it works all except for one minor difference. Here is what happens accessing my RadSchedulers via our remote web server:
But for New and Edit, the appointment window won't popup. This happens for all client web browsers, Safari, IE, Chrome. It happens on different client machines and for different users. So it feels like the problem is something on the web server, not a client side problem. Could there be some kind of deployment issue? Something I didn't deploy properly? Is the production web server running a different version of required DLL's?
This works perfectly on my developer machine within Visual Studio, so I know this should work. I've never had any problems creating or editing appointments when running locally on my test virtual machine developer environment. So I think my aspx and c# code is correct, since it works locally. Another test scenario is from my developer machine, hit the production web site. The same problem occurs. So my developer machine also fails when hitting the production web URL. But not within Visual Studio.
Thanks for your help.
- A user will right click on an existing appointment (or empty space). This shows the New Appointment / Edit / Delete context menu choices. Click Edit. The New/Edit/Delete menu disappears. (so far so good). But then, nothing happens. The modal default Appointment editor window never appears. No error gets thrown, I don't see any errors in the web browser status bar. I've done this so many times and it never appears, regardless of what appointment in my scheduler that I choose.
- Same problem for New Appointment. Nothing happens after the context menu disappears.
- However, if you click Delete, the confirmation window appears: "Are you sure you want to delete this appointment?" . I click OK and it works fine, the appointment gets deleted.
But for New and Edit, the appointment window won't popup. This happens for all client web browsers, Safari, IE, Chrome. It happens on different client machines and for different users. So it feels like the problem is something on the web server, not a client side problem. Could there be some kind of deployment issue? Something I didn't deploy properly? Is the production web server running a different version of required DLL's?
This works perfectly on my developer machine within Visual Studio, so I know this should work. I've never had any problems creating or editing appointments when running locally on my test virtual machine developer environment. So I think my aspx and c# code is correct, since it works locally. Another test scenario is from my developer machine, hit the production web site. The same problem occurs. So my developer machine also fails when hitting the production web URL. But not within Visual Studio.
Thanks for your help.