Thanks for taking the
time to reply. I have a good feeling the solution is close at
hand.
I can understand the reasoning behind the need for the
skin/container to register the use of runtime
components - jQuery in this case. Presumably the registration
step was not done for the Mandeeps Portfolio.ascx container that encloses the
HTML module. This would explain why the filter function does NOT work
outside a DNN session, but it does not explain why the other major
browsers work on their own without the help of DNN to provide access to jQuery. Your comment on this observation? Also, why
is the Internet Explorer a special case here?
Using the information you provided I
modified the (so-called) DIXIT Portfolio container to include the registration
statements. See below. Unfortunately however, this did not solve the problem. Have I entered something incorrectly?
<%@ Control Language="vb"
CodeBehind="~/admin/Containers/container.vb"
AutoEventWireup="false" Explicit="True"
Inherits="DotNetNuke.UI.Containers.Container" %>
<%@ Register TagPrefix="dnn"
TagName="JQUERY" Src="~/Admin/Skins/jQuery.ascx" %>
<dnn:JQUERY ID="dnnjQuery"
ScriptType="jQuery" runat="server" />
<dnn:JQUERY ID="isotope"
ScriptType="other" Path="Skin" location="js/jquery.isotope.min.js" name="isotope"
Order="e_Default" runat="server" />
<dnn:JQUERY ID="sorting"
ScriptType="other" Path="Skin" location="js/sorting.js" name="sorting"
Order="e_Default" runat="server" />
<script type="text/javascript" src="<%=
ContainerPath %>js/jquery.isotope.min.js"></script>
<script type="text/javascript" src="<%=
ContainerPath %>js/sorting.js"></script>
<div id="ContentPane"
runat="server">
</div>
<div class="clear">
</div>