如何在 dotnetnuke 中创建门户模板来保留每个第三方模块？设置
我正在开发 Dotnetnuke (05.06.01) 网站，其中将包含约 200 个门户，在创建门户时，它们将由准备好的四个门户模板生成。 问题就在那时出现了。我有一些第三方模块，当我创建门户模板文件时，它们的设置未在门户模板中设置。我怎样才能克服这个问题？
I am developing Dotnetnuke (05.06.01) site which will have ~200 portals in it, while the portals are created, they will be produced from prepared four portal templates.
The problem arises at that point. I have some 3rd party modules and when i created portal template file their settings are not set in portal template. How can I overcome this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这很奇怪。模块和选项卡模块设置应该出现在门户模板中。这些都是由同一个第三方提供的，还是来自不同的开发商？也许其中一位开发人员正在使用一种不常见的解决方案来存储设置，但我通常不希望出现这种情况。但是，我确实知道门户设置不会存储在门户模板中（因此，如果模块的设置似乎在门户范围内，这可能就是问题所在）。
不幸的是，如果设置没有完成，您无能为力（您无法强制模块在其他地方查找设置）。也许如果您可以找到存储设置的位置，您可以在创建门户后将它们恢复为手册，但我怀疑是否有办法将它们包含在门户模板中（如果它们不是）自然而然就过来了。
That's strange. Module and Tab Module settings should come across in the portal template. Are these all by the same 3rd party, or from different developers? Perhaps one of the developers is using an uncommon solution for storing settings, but I wouldn't expect that in general. I do know, however, that portal settings don't get stored in the portal template (so if the modules' settings seem portal-wide in scope, that might be the issue).
Unfortunately, if the settings aren't coming over, there's not much that you can do (you don't be able to force the module to look elsewhere for the settings). Perhaps if you can find where the settings are being stored, you can restore them as a manual after creating the portal, but I doubt that there's a way to include them in the portal template if they aren't coming over naturally.
这是由于 DotNetNuke 模板系统工作方式的继承限制造成的。仅当相关模块的开发人员以允许它们成为模板一部分的方式存储实际设置时，才会保存实际设置。
这是由开发人员构建模块的方式控制的，如果您使用的模块不支持它，您将无法更改此行为。
This is due to an inherit limitation in the way that the DotNetNuke template system works. The actual settings will only be saved if the developer of the module in question stored them in a manner that allows for them to be part of the template.
This is controlled by the way the developer builds their modules and if the modules you are using do not support it, you will not be able to change this behavior.
正如米切尔所说，您需要手动找出受影响的模块存储其设置的位置，并编写一个脚本来自己传播这些设置。
As Mitchel says, you'll need to manually work out where the affected modules are storing their settings, and come up with a script to propagate those settings yourself.
谢谢您的回复。
如果模块正在实现Iportable Interface（如果您在模块设置中看到导入内容/导出内容，则该模块正在实现 Iportable），并且在导出时如果您选择“包含内容”模块设置保存到门户模板文件，否则不保存。
谢谢大家...
Thank you for your replies.
If a module is implementing Iportable Interface (if you see import content/export content in Module settings then that module is implementing Iportable) and while exporting if you choose "include content" module settings are saved to portal template file, otherwise it is not.
thank you all...