Support Center

Adding Existing Module

Embed one or multiple DNN Modules in content. Either stack Modules one below another or wrap DNN Modules within HTML Content like a Module Wrapper.

Navigate to Manage > Modules

Easily show existing DNN modules that are on same page as Live HTML module, on a remote page, or even another portal on same DNN Installation.

Select the portal, page, and DotNetNuke module from the list and Click Add Module button

Note: Only a Host/Superuser can add modules from another Portal. A portal list will appear if you're logged in as host. 

Tag Name: is used to wrap modules with other arbitrary HTML Content. Refer to Wrapping Modules for more information. 

Show Module Container: shows the original module container when embedded within Live HTML

Enforce Start/End Date: Enforces the original start/end date of the embedded modules. 

Enforce Module Permissions: Enforces the original module permissions of the embedded modules.

Inject Event: This should always be set to "Automatic". Refer to technical notes below for advanced users:

Technical Notes: Embedded modules are injected on the page either at Page_Init or Page_Load event of ASP.NET page life cycle. Live HTML automatically determines the appropriate event based on the "Supports Partial Rendering" property of the module's control. If a module supports partial rendering then it must be injected at Page_Init; otherwise, it is injected at Page_Load. The problem arises with few modules that do not "Support Partial Rendering" in module's control but dynamically introduce AJAX components at run time which causes Live HTML to inject the module at incorrect event. 

Advanced users can force Live HTML to inject the module at a particular event: Page_Init or Page_Load

Existing Module

Important Notes: DNN API's does not officially support embedding a module within another module. Therefore, there are few limitations to embedding modules withing Live HTML. 

  • Embedded modules that are on same page as Live HTML can be edited/managed from within Live HTML; all other embedded modules (those that are on other pages) must be edited/managed on their original page. 
  • Live HTML will automatically hide any embedded modules that are on the same page as Live HTML's module; however, due to technical limitations, only embedded modules up to 2 level deep can be hidden. If you're nesting modules beyond 2 level then move the embedded modules to other page. 

Glad we could be helpful. Thanks for the feedback.

Sorry we couldn't be helpful. Your feedback will help us improve this article.

How helpful was this page?

  
Updated on Tue, 20 Mar 2018 by Khushi Singh