网站上缺少 Dotnetnuke 操作按钮

发布于 2024-10-07 13:42:38 字数 669 浏览 5 评论 0 原文

我正在一个项目中使用 DNN 5.1,但发生了一些我不太明白的事情。控制任何 html 模块操作的控制按钮丢失了。如果我检查 DNN 的事件查看器,我会得到以下结果:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set 
to an instance of an object. ---> System.NullReferenceException: Object reference not    
set to an instance of an object. at otNetNuke.UI.Containers.ActionBase.get_ActionRoot() 
at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at 
DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- 
End of inner exception stack trace

这似乎是皮肤文件的问题,因为如果我切换到另一个皮肤,操作按钮会恢复正常。但我不明白的是,自上次成功使用它以来,情况发生了怎样的变化。

如果有人有一些建议,我将不胜感激。

I am using DNN 5.1 on a project and something's happened that I cannot quite figure out. The control button which controls the actions of any html module has gone missing. If I check the event viewer of DNN, this is what I get:

Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set 
to an instance of an object. ---> System.NullReferenceException: Object reference not    
set to an instance of an object. at otNetNuke.UI.Containers.ActionBase.get_ActionRoot() 
at DotNetNuke.UI.WebControls.SolPartActions.BindMenu() at 
DotNetNuke.UI.WebControls.SolPartActions.Page_PreRender(Object sender, EventArgs e) --- 
End of inner exception stack trace

It seems to be a problem with the Skin file because if I switch to another skin ,the Actions button is back as normal. What I am not getting though is how this has changed since the last time I successfully used it.

If someone has some suggestions I would appreciate it.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

醉城メ夜风 2024-10-14 13:42:38

我建议查看您的模块容器 .ascx 文件并删除对 solpart 的引用!并更换为不同的提供商。我发现标准的速度非常慢。我将从我的一个容器 .ascx 文件中获取代码供您检查 - 这使用另一个菜单提供程序来处理小管理菜单,

<%@ Control Language="vb" Codebehind="~/admin/Containers/container.vb" AutoEventWireup="false"
    Explicit="True" Inherits="DotNetNuke.UI.Containers.Container" %>
<%@ Register TagPrefix="ddr" TagName="ACTIONS" src="~/DesktopModules/DDRMenu/Actions.ascx" %>
<%@ Register TagPrefix="dnn" TagName="TITLE" Src="~/Admin/Containers/Title.ascx" %>
<%Dim ModuleTitle As String = DotNetNuke.UI.Containers.Container.GetPortalModuleBase(dnnTITLE).ModuleConfiguration.ModuleTitle()%>
<dnn:title runat="server" id="dnnTitle" visible="false" />                
<h3><%= ModuleTitle %></h3>
<div class="tab_edging" id="ContentPane" runat="server" style="border:1px solid white">
</div>      
<div class="spacer">
<ddr:ACTIONS runat="server" />
</div>

我们已经从 http://www.dnngarden.com/Download.T87.aspx 我建议你看看!

I would suggest looking into your module container .ascx file and remove the references to solpart! and replace with a different provider. I find the standard ones are very slow. I will grab the code from one of my container .ascx files for you to examine - this uses another menu provider to handle the little admin menu's

<%@ Control Language="vb" Codebehind="~/admin/Containers/container.vb" AutoEventWireup="false"
    Explicit="True" Inherits="DotNetNuke.UI.Containers.Container" %>
<%@ Register TagPrefix="ddr" TagName="ACTIONS" src="~/DesktopModules/DDRMenu/Actions.ascx" %>
<%@ Register TagPrefix="dnn" TagName="TITLE" Src="~/Admin/Containers/Title.ascx" %>
<%Dim ModuleTitle As String = DotNetNuke.UI.Containers.Container.GetPortalModuleBase(dnnTITLE).ModuleConfiguration.ModuleTitle()%>
<dnn:title runat="server" id="dnnTitle" visible="false" />                
<h3><%= ModuleTitle %></h3>
<div class="tab_edging" id="ContentPane" runat="server" style="border:1px solid white">
</div>      
<div class="spacer">
<ddr:ACTIONS runat="server" />
</div>

we have installed an extra menu provider from http://www.dnngarden.com/Download.T87.aspx which i suggest you take a look at!

回首观望 2024-10-14 13:42:38

问题可能是容器或一些错误的 javascript。我会首先尝试切换到不同的默认容器。如果这不起作用,请查看是否有任何 Javascript 抛出错误(我通常在 Firefox 错误控制台中执行此操作,但有很多方法)。

The problem is probably the container or some errant javascript. I would try switching to a different default container first. If that doesn't do it, look to see if there is any Javascript that is throwing errors (I generally do this in the Firefox Error console, but there are many ways).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文