DotNetNuke - 模块设置在新用户控件上消失
我有一个 DNN 模块，它呈现用户控件 (view.ascx)
一切正常（我已登录）并且我获得了 DNN 设置菜单。
但是，当我添加另一个控件并像这样加载它时：
string url = Globals.NavigateURL(PortalSettings.ActiveTab.TabID, "View_Details", "mid=" + ModuleId.ToString());
Response.Redirect(url);
加载新控件时我会丢失设置链接。
有什么想法吗？是否有某个属性可以打开加载的用户控件的设置？
I have a DNN module which renders a user control (view.ascx)
All is ok ( I am logged in ) and I get the DNN settings menu.
however when I add another control and load it like so:
string url = Globals.NavigateURL(PortalSettings.ActiveTab.TabID, "View_Details", "mid=" + ModuleId.ToString());
Response.Redirect(url);
I lose the settings link when the new control loads.
Any ideas? Is there a property somewhere to turn on settings for the loaded user control?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当查询字符串中有“mid”时，您将使用模块隔离（即模块控件将显示在编辑皮肤的 ContentPane 中，并且将是页面上的唯一模块）。当处于模块隔离时，操作菜单不包含设置。这只是 DNN 的一个事实。
你有几个选择。首先，您可以选择另一种导航方法（请参阅 Michael Washington 的旧版（但仍然不错）适合您的模块导航选项DotNetNuke® 模块文章）。
其次，您可以将自己的链接添加到该控件上的“设置”。您也许可以实现
IActionable并将其添加回操作菜单（我不确定这是否有效），或者您可以向模块添加某种按钮或导航栏（可能在所有控件上保持一致性）。您是为一般 DNN 社区还是为不熟悉 DNN 的客户设计此模块？具有 DNN 经验的人不会期望能够访问模块“内部”的设置。
When you have "mid" in the querystring, you're going to be using module isolation (i.e. that module control will show up in the edit skin's ContentPane and will be the only module on the page). When in module isolation, the action menu doesn't include settings. This is just a fact of DNN.
You have a couple of options. First, you could choose another navigation method (see Michael Washington's old (but still good) Module Navigation Options for your DotNetNuke® Module article).
Second, you could put your own link to the Settings on that control. You may be able to implement
IActionableand just add it back to the action menu (I'm not sure if that would work), or you can add some sort of button or navigation bar to your module (potentially on all of the controls for consistency).Are you designing this module for the general DNN community, or for a client that isn't familiar with DNN? People with DNN experience won't expect to be able to get to the settings one they're "inside" a module.