Hi Telerik-Community
We have built an asynchronous implementation of SharePoint's document library web part using the Telerik ASP.NET AJAX components to avoid all the unnecessary postbacks (besides eleminating other issues). The newly created web part works fine, but as soon as I add it to a web part zone on a page, I get JavaScript errors caused by the functions handling the onMouseOver and onMouseOut events for the <SharePoint:AspMenu>. This happens even with the default master page and a common page layout. Are there any known issues on this? Does anybody have any hints what might have gone wrong and how to fix it?
Kind regards,
Thomas
We have built an asynchronous implementation of SharePoint's document library web part using the Telerik ASP.NET AJAX components to avoid all the unnecessary postbacks (besides eleminating other issues). The newly created web part works fine, but as soon as I add it to a web part zone on a page, I get JavaScript errors caused by the functions handling the onMouseOver and onMouseOut events for the <SharePoint:AspMenu>. This happens even with the default master page and a common page layout. Are there any known issues on this? Does anybody have any hints what might have gone wrong and how to fix it?
Kind regards,
Thomas
1 Answer, 1 is accepted
0
Tom
Top achievements
Rank 1
Rank 1
answered on 15 Sep 2009, 01:55 PM
Phu, we finally found the cause for this issue... It was all about a missing HttpHandlers-entry in
web.config for the ScriptResource.axd. The final hint was found in http://blogs.telerik.com/blogs/posts/08-07-18/web_resources_demystified_part_3_troubleshooting.aspx under "Dealing with the 404 error code (the requested URL was not found)", even if we didn't get a 404.
FYI: A similar issue is discussed here: http://forums.asp.net/t/1009084.aspx
web.config for the ScriptResource.axd. The final hint was found in http://blogs.telerik.com/blogs/posts/08-07-18/web_resources_demystified_part_3_troubleshooting.aspx under "Dealing with the 404 error code (the requested URL was not found)", even if we didn't get a 404.
FYI: A similar issue is discussed here: http://forums.asp.net/t/1009084.aspx