I finally tracked down why Gallery 4.04.00 pop-up slideshows are failing when installed in DNN 6.01.00 or 6.01.00. Gallery implements its own pop-ups using a base page (GalleryPage.aspx) which is follows the markup of DNN's Default.aspx page to be able to take advantage of the core API's for localization and the loading of CSS style sheets and Javascripts. In Gallery 4.04.00 I converted the slideshow to make use of the jQuery framework script which was being loaded into the pop-up page's header via the following calls:
If isPopup Then
DotNetNuke.Framework.jQuery.RegisterScript(Page)
Else
DotNetNuke.Framework.jQuery.RequestRegistration()
End If
Since GalleryPage.aspx was designed to include an asp:placeholder control (with id="SCRIPTS") in the page header this worked fine up through and including DNN 6.01.00 BETA. However, with DNN 6.01.00 RELEASE and 6.01.01, the DotNetNuke.Framework.jQuery.RegisterScript method was deprecated and re-coded to call the new ClientResourceManager.RegisterScript method which requires an asp:placeholder control (with id="ClientDependencyHeadJs") in the page header. Since this placeholder is not found in GalleryPage.aspx, jQuery never gets loaded.
One workaround that would not require a re-compilation and repackaging of the Gallery module would be to include the following markup within the <head> . . . </head> elements of GalleryPage.aspx to force the loading of jQuery,.js for all Gallery pop-ups:
<script src="/Resources/Shared/Scripts/jquery/jquery.min.js?1.6.1" type="text/javascript"></script>
A more satisfactory solution would be to modify GalleryPage.aspx to include the new placeholder controls and modify ControlSlideShow.ascx.vb to use the new ClientDependencyManager to properly register jQuery. This would, however, require a re-compile and re-packaging plus resubmission of the module through the DNN release tracker testing process. Because my plans for Gallery are to concentrate on building a completely new Gallery 5 (or more likely Gallery 6) module not based on the existing Gallery's legacy code, I do not expect to release a fix for this one issue.