Glossary

The set of menus that provides access to the functionality of a module. Available only if the page is in Edit mode. The menus can include the Edit menu (pencil icon), the Manage menu (gear icon), and the Move menu (four-arrow icon). The DNN Platform provides actions that are common to all modules; however, a module might provide additional actions. If the module instance is independent, then actions performed through the module action menu affect only that specific module instance in that specific webpage. If the same module instance is referenced in multiple pages, then changes made to the module instance from any of those pages are reflected in all those pages.

A set of related components that define the look and feel of a module. In contrast, a skin or theme defines the look and feel of an entire webpage or website.

A token used in database scripts to refer to the SQL Server database schema that is used during DNN installation. Default: dbo.

A score that measures how involved the member is with the rest of the community.

A combination of themes, modules, or other components that replace or extend specific features of the DNN Platform.

A URL that hides a coded path. Example: http://www.example.com/myanswerpage might actually resolve to http://www.example.com/default.aspx?tabid=42. DNN provides three modes of friendly URLs:

• Advanced provides both human-friendly and search-friendly URLs.
• HumanFriendly uses simple URLs for page names and uses tabid in more complicated URLs. Limited redirect support.
• SearchFriendly includes tabid patterns in URLs.

The list of open-source extensions (including modules and themes) from the DNN community.

A score that measures the positive or negative effect of the member on the community.

An XML file (e.g., MyExtension.dnn) that specifies how to install an extension. The manifest contains information regarding the extension type, and the various components that make up the extension.

A DNN extension that provides content or some functionality in a page. Example: A module could produce dynamic content that is displayed in a pane on the page.

A custom string used as a prefix to names of DNN-related SQL objects, such as tables and stored procedures. This allows you to identify the DNN objects in a database that supports other applications besides DNN. Default: blank.

The zip file that contains all files required to install an extension in a DNN-based website. Also, a section of the DNN Manifest schema that specifies how the core components of the extension are installed.

A layout template area that holds a module. Theme designers determine the names and positions of panes. Administrators and webpage editors select the pane for each module added to the webpage. When the webpage is viewed, the pane can display content, depending on the module's functionality.

A URL that refers to a specific website in a DNN installation. Examples: http://www.example.com (parent portal alias), http://www.example.com/pathname (child portal alias). Each website can have one or more portal aliases.

A type of DNN extension that provides an alternative implementation of a specific functionality of the DNN Platform. Examples: authentication providers, data providers, and navigation providers. In most cases, even if multiple implementations are available in a DNN installation, only one implementation of each provider type is active at any time.

A module setting that indicates that use of the module can be restricted for security reasons. Example: Modules that expose confidential user information and modules that manage security access to the site should be premium.

In an HTML content template, a placeholder for data to be injected into the HTML output. Example: [User:UserName] is replaced with the actual username.

In an HTML layout template, a word that represents DNN-standard code for a theme object. Examples: [NAV], [COPYRIGHT], [LOGIN], [PRIVACY], [TERMS], and [SEARCH].

In a Visualizer template, a word that represents a field in the content type associated with the visualizer. Example: If the content type field is named Meeting Timeslot, the field's token would be {{ meetingTimeslot }}.