Hello,
For some reason when I add a module to the ContentPane of my skin none of the buttons or links seem to work.  If I move the module to a different section, like the ArticlePane, then all the buttons work.  Has anyone seen anything like this before?  Is there some place I can look that might be telling that div to act differently?
            <h1 class="CategoryHeading"></h1>
            <div id="ContentPane" runat=server/>           
            <div id="CallToActionPane" runat="server" class="c2a desktop" />
            <div id="ArticlesPane" runat="server" class="articles" />
Thanks,
Alex

Thanks, I'm sure that was probably one of my problems, but after fixing that and restarting the application it's still doing the same thing. The module works as far as the display goes, but the links and checkboxes act like they are disabled. The cursor doesn't change to a pointer when hovering over the controls and clicking them does nothing. This started after upgrading to DNN 9 from 7.

Evidently, if I remove the CallToActionPane it works. I guess it's overlapping the ContentPane. I wonder what changed between the versions to cause this, though. I have both a DNN 7 and 9 version running locally, the skin is the same. In both versions the div highlighted in chrome dev tools looks like the CallToActionPane overlaps, but the buttons still work in 7. I don't know, but maybe I'm on the right track looking at the css. Thanks