We are performing an upgrade from 4.0.2 to 5.6.1 for a client who also has some custom modules built using Atlas (the early version of AJAX for .NET).   Our upgrade path took us from 4.0.2 to 4.9 to 5.6.1.   The data and everything seems to be accurate but the custom modules that worked fine in 4.0 and 4.9 are no longer working.   The issue seems to be that the ContentPane is wrapped in the UpdatePanel and therefore is not being found by DNN and we are getting the error that it 'Cannot Find the ContentPane'.   While this would probably be done differently today, the module that utilizes the AJAX lives in this pane, so this is why they did it this way (I guess). 

We've tried removing the references to Atlas and just using regular AJAX but that doesn't work either.  Anyone else have an issue like this?


Here is a code snip:

<asp:UpdatePanel id="UpdatePanel1" runat="server" UpdateMode="Conditional" Visible="true">

<ContentTemplate>

<div id="ContentPane" runat="server"></div>

</ContentTemplate>

</asp:UpdatePanel>

Thanks!

Thanks Robert! Your answer was helpful because not only did it make sense to remove the UpdatePanels (which we tried before), it also put me in the right place to find what was wrong with the module after that issue was taken care of. The module itself didn't have a direct reference to it's source code so it wasn't showing up on the page.