dotnetnuke模块开发
好的，我的页面左侧面板中有一个新闻模块。要查看详细信息，我想在中间窗格中打开它。
我目前所做的是创建一个新模块并在其中创建一个详细信息页面以在中间窗格中打开。在这种情况下我可以使用更好的技术吗？这样我就可以在当前模块中创建一个详细信息页面，并使其在中间窗格中打开，而不是在同一窗格中打开。我正在使用 dotnetnuke 版本 6.0.2。
ok i have a news module in the left panel of my page. To view the details i want to open it in the middle pane.
what i have currently done is to create a new module and make a detail page in it to be opened in the middle pane. Is there any better technique that I can use here in this scenario ? so that I can create a detail page in the current module and make it open in the middle pane not in the same pane as it is . I am using dotnetnuke version 6.0.2.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在查看模块内容时，您想保留左侧的“列表”，还是只显示中间的详细信息？
一种方法可能是使用主页上新闻模块的 RSS 提要，然后将文章模块本身放在“中间”窗格的另一个页面上。用户从主页单击 RSS，这会将他们带到文章/详细信息页面。
另一种方法是在模块包中包含两个模块，一个称为文章列表，另一个称为文章显示。文章列表将与 DotNetNuke.Common.Globals.NavigateURL(TabId, "", "ArticleId="+ArticleId.ToString()); 之类的内容建立链接
然后，您的文章详细信息视图模块将隐藏自身，除非文章 ID 作为 URL 中的查询字符串参数传入。
另一种方法是在模块定义中包含多个“视图”控件，第一个在定义中没有“ControlKey”，使其成为默认视图。然后有一个名为“Details”的“ControlKey”。让您的列表使用 EditUrl("Details","ArticleId="+ArticleId.ToString(); 建立链接
这将使 DNN 在页面的内容窗格中加载详细信息视图，但不会在页面上加载其他模块。
Do you want to keep the "list" on the left, or just display the detail in the middle when viewing the contents of the module?
One approach, might be to use the RSS feed from your news module on a Home page, then have your article module itself on another page in the "middle" pane. A user clicks on the RSS from the home page and that would take them to the article/detail page.
Another approach would be to have two modules in your module package, one called Article List, and one called Article display. Article List would build links with something like DotNetNuke.Common.Globals.NavigateURL(TabId, "", "ArticleId="+ArticleId.ToString());
Then your article detail view module would hide itself, unless the Article ID was passed in as a querystring parameter in the URL.
Another approach, would be to have multiple "View" controls within your Module Definition, the first having no "ControlKey" in the definition, making it the default view. Then have a "ControlKey" called Details. Have your list build a link with EditUrl("Details","ArticleId="+ArticleId.ToString();
This would have DNN load the details view, in the Content Pane of the page, but not other modules would load on the page.