Michael Hanson
Top achievements
Rank 1
Rank 1
Michael Hanson
asked on 22 Sep 2007, 06:01 PM
I have installed the latest versions of RadControls for ASP.NET and Prometheus. I have added a Scheduler to a new page, and bound it to a datasource and it retrieves data fine. I can also insert, update and delete appointments.
BUT the Day, Week and Month view buttons/tabs do nothing, similarly the next, previous and Show 24 Hours options do nothing.
I don't doubt I have missed something with configuring the scheduler, but I have copied the sample sites as closely as possible and migrated all web.config sections and keys to the one for my application.
My first thought was that it was a WebResource.axd access problem as it seemed some scripts weren't loading but as the edit side of things works I am fairly confident this is not the problem.
Any ideas?
BUT the Day, Week and Month view buttons/tabs do nothing, similarly the next, previous and Show 24 Hours options do nothing.
I don't doubt I have missed something with configuring the scheduler, but I have copied the sample sites as closely as possible and migrated all web.config sections and keys to the one for my application.
My first thought was that it was a WebResource.axd access problem as it seemed some scripts weren't loading but as the edit side of things works I am fairly confident this is not the problem.
Any ideas?
3 Answers, 1 is accepted
0
Hello,
You are right - if appointment modifications work properly, it's not a script loading issue.
Theoretically, it is possible for some CSS styles to interfere with the previous/next buttons, but the "Show 24 Hours" button should not be affected by CSS.
Can you please open a support ticket and send us a project showing the issue you are having, so we can debug it locally? This will help us pinpoint the problem much quicker.
Best wishes,
Dimitar Milushev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
You are right - if appointment modifications work properly, it's not a script loading issue.
Theoretically, it is possible for some CSS styles to interfere with the previous/next buttons, but the "Show 24 Hours" button should not be affected by CSS.
Can you please open a support ticket and send us a project showing the issue you are having, so we can debug it locally? This will help us pinpoint the problem much quicker.
Best wishes,
Dimitar Milushev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Michael Hanson
Top achievements
Rank 1
Rank 1
answered on 26 Sep 2007, 06:48 PM
I had already submitted a support ticket because this post got no response. In the end I found the problem on my own by process of elimination, but I didn't find it until I finally started commenting out one line at a time in my web.config file. Eventually I removed the <pages theme="Default" /> entry and it worked. I then put the entry back and excluded each one file in my theme folder at a time until it worked. The file turned out to be my Default.skin file where I put definitions for all the variations of standards ASP.NET controls. I commented all definitions out then added them back one at a time until I found the one causing the problem. It was the following definition:
<asp:hyperlink runat="server" cssclass="skinHyperlinkStyle" />
I cleared everything from the class in the CSS stylesheet but the Scheduler still didn't work. Only when I removed the definition did it work again.
In response to and update to my support ticket I was told that EnableTheming="false" would solve the problem which it did. However I would have to consider it a bug if any of my software stopped working just because a definition in a skin file existed but didn't change the control in any way.
<asp:hyperlink runat="server" cssclass="skinHyperlinkStyle" />
I cleared everything from the class in the CSS stylesheet but the Scheduler still didn't work. Only when I removed the definition did it work again.
In response to and update to my support ticket I was told that EnableTheming="false" would solve the problem which it did. However I would have to consider it a bug if any of my software stopped working just because a definition in a skin file existed but didn't change the control in any way.
0
Hello Michael Hanson,
I agree that this problem appears to be quite hard to diagnose and debug. We are really amazed how accurately you've managed to point it out. Unfortunately, this is the way ASP.NET theming works. The theme applies to all child controls and RadScheduler happens to have HyperLink children, so it is not a bug per se.
Greetings,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I agree that this problem appears to be quite hard to diagnose and debug. We are really amazed how accurately you've managed to point it out. Unfortunately, this is the way ASP.NET theming works. The theme applies to all child controls and RadScheduler happens to have HyperLink children, so it is not a bug per se.
Greetings,
Tsvetomir Tsonev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center