I’m a novice Container/Skins developer, and I’ve got an issue where the content of the SearchResults module is overrunning the border of my installed container. I believe it is the telerik paging control -- that’s meant to allow users to page thorugh large results sets -- that’s causing the problem.
I’m working on DNN version 6.1.5.
Here’s my ascx for the container:
<%@ Control language="vb" AutoEventWireup="false" Explicit="True" Inherits="DotNetNuke.UI.Containers.Container" %>
<%@ Register TagPrefix="dnn" TagName="TITLE" Src="~/Admin/Containers/Title.ascx" %>
<%@ Register TagPrefix="dnn" TagName="ACTIONS" Src="~/Admin/Containers/Actions.ascx" %>
<%@ Register TagPrefix="dnn" TagName="ACTIONBUTTON" Src="~/Admin/Containers/ActionButton.ascx" %>
<%@ Register TagPrefix="dnn" TagName="VISIBILITY" Src="~/Admin/Containers/Visibility.ascx" %>
<dnn:ACTIONS runat="server" id="dnnACTIONS" ProviderName="DNNMenuNavigationProvider" ExpandDepth="1" PopulateNodesFromClient="True" />
<div class="greenhead">
<div class="visi"><dnn:VISIBILITY runat="server" id="dnnVISIBILITY" MinIcon="images/min.png" MaxIcon="images/max.png" /></div>
<h3><dnn:TITLE ID="dnnTitle" runat="server" cssclass="ctitle" /></h3>
</div>
<div class="c_greenbox">
<div class="Middle">
<div id="ContentPane" runat="server" class="containerpane"></div>
</div>
</div>
<div class="c_footer">
<dnn:ACTIONBUTTON runat="server" id="dnnACTIONBUTTON1" CommandName="AddContent.Action" DisplayIcon="True" DisplayLink="True" />
<dnn:ACTIONBUTTON runat="server" id="dnnACTIONBUTTON2" CommandName="SyndicateModule.Action" DisplayIcon="True" DisplayLink="false" />
<dnn:ACTIONBUTTON runat="server" id="dnnACTIONBUTTON4" CommandName="ModuleSettings.Action" DisplayIcon="True" DisplayLink="false" />
<dnn:ACTIONBUTTON runat="server" id="dnnACTIONBUTTON3" CommandName="PrintModule.Action" DisplayIcon="True" DisplayLink="false" />
</div>
Here’s the CSS:
.greenhead{ background:url(images/greenh.gif) 0 0 repeat-x;
padding:5px 10px;
-webkit-box-shadow: #00362b 0px 2px 3px;
-moz-box-shadow: #00362b 0px 2px 3px;
box-shadow: #00362b 0px 2px 3px;
-webkit-border-top-left-radius:6px;
-webkit-border-top-right-radius:6px;
-moz-border-top-left-radius:6px;
-moz-border-top-right-radius:6px;
border-top-left-radius:6px;
border-top-right-radius:6px;
border-radius: 6px 6px 0 0;
behavior: url(/pie.htc);
color:#fff;
border-bottom:none
}
.c_greenbox{
border: 2px solid #00362b;
padding: 10px;
-webkit-box-shadow: #00362b 0px 2px 3px;
-moz-box-shadow: #00362b 0px 2px 3px;
box-shadow: #00362b 0px 2px 3px;
background: #fff;
-webkit-border-bottom-left-radius:6px;
-webkit-border-bottom-right-radius:6px;
-moz-border-bottom-left-radius:6px;
-moz-border-bottom-right-radius:6px;
border-bottom-left-radius:6px;
border-bottom-right-radius:6px;
border-radius: 0 0 6px 6px;
behavior: url(/pie.htc);
border-top:none
}
When there’s no search results, the “no results message box sits nicely inside my container, but the telerik table pager runs outside. It even extends out past our top-level container. When there is results, the rows of the results table also extend ;over all parent container borders.