Hi,

For some reason, I can't find a way to create a pagetemplate holding the modules and the module settings.

I think i am doing something wrong, looking the wrong way or ... 

DNN is quite new to me, I am still scratching the surface to explore its capabilities.

So please forgive me, if i am being stupid on this one...

Goal:

Creating and using a page template with a module including the module settings.

Applies to:

• Media module
• SQL module

Does not seem to apply to:

• Html module 

Methods used:

• Export page, import page
• Copy page

Problem:

After creating a page with a SQL and a Document module and exporting it (with content included) I get not quite what i want.

I would like to have gotten a copy of the page with the SQL-statement included, but I get a page with just the 2 modules...

Later on i tested it with another page, containing a html module and a Media module, the html gets restored (copied) , but the images are not. (?)

Am I missing the option Include settings, is this a bug, or ...?

When I Copy the page using the Copy wizard I get the same result.  

How to reproduce it / what i did...:

1. Log on as Host (to be able to write sql later on...)
2. Create a new page (tab)
3. Add a SQL module to the page
4. Apply the following settings: 
   • Title:  [ simple foto viewer ]
   • Description [  ]
   • Allowed URL Parameters [ ]
   • Active Data Source: [DotNetNuke Data Source]

   • Query: 

     SELECT dnn_Documents.Title AS [DocTitle], dnn_Documents.Description AS [DocDescr], dnn_Files.PortalID AS [PortalID], dnn_Files.Folder AS [FolderName], dnn_Files.FileName AS [FileName], dnn_Files.Size AS [FileSize], dnn_Files.Width AS [ImageWidth], dnn_Files.Height AS [ImageHeight] FROM dnn_TabModules LEFT JOIN dnn_Documents ON dnn_Documents.ModuleID = dnn_TabModules.ModuleID RIGHT JOIN dnn_Files ON dnn_Documents.URL = ('FileID=' + CAST(dnn_Files.FileID as varchar(30))) WHERE dnn_TabModules.TabID = @TabID AND dnn_TabModules.ModuleID != @ModuleID AND dnn_TabModules.Isdeleted = 0 AND dnn_Files.PortalID = @PortalID
   • Html Decode [ ]
   • Html Encode [ ]
   • Caching [ ]
   • Show Info Pane [ ]
   • Show Controls [ ]
   • Auto Run Report [v] 
   • Active Visualizer [ XSL Transformation Visualizer ] 
   • File location: [ Reports/Photoalbum ]
   • File Name : [ Photoalbum.xsl]
   • xml Namespace: []
   • .Net Type : [ ] 
5. Add a Document Module
6. Apply the following settings:
   • Module title: [Manage photo's on this page]
   • Give edit rights to the users who may add, edit and delete photos
   • Do not add photos 
7. Export the page using the export button (left on top of the page, using the default DNN skin)
8. Use the following options:
   • Folder: [templates]
   • Template name: [ Photo album ]
   • Include content [v]
9. Import the module as a new page

The result at point 8 is a template (xml-file) with the SQL-statement included, the result at point 9 is a page with the SQL-module telling me I should enter a SQL statement...

All steps are taken as "host".

Environment:

DotNetNuke Product: DotNetNuke Community Edition

DotNetNuke Version: 5.1.0

Host GUID:

CAS Permissions: ReflectionPermission, WebPermission, AspNetHostingPermission

Data Provider: SqlDataProvider

Caching Provider: FileBasedCachingProvider

Logging Provider: DBLoggingProvider

Html Editor Provider: FckHtmlEditorProvider

Friendy Url Provider: DNNFriendlyUrl

Friendly URLs Enabled: True

Friendly URL Type: humanfriendly

Scheduler Mode: REQUEST_METHOD

Web Farm Enabled: True

OS Version: Microsoft Windows NT 5.2.3790 Service Pack 2

Web Server Version: Microsoft-IIS/6.0

.NET Framework Version: 2.0.50727.3053

ASP.NET Identity: NT AUTHORITY\Netwerkservice

Host Name:

Physical Path:

Site Url:

Relative Path: /

Server Time: 7/14/2009 4:13:02 PM

Kind regards,

Luciano

Dear Sebastian, 

Thanks for the quick and accurate answer. 

The funny thing about this is, the modules (at least the ones I did test) handle its specific settings' ([modulename] Module Settings) as 'content' when using the export / import functionality.

In a way it is logical, just something to take into account, when creating a page template.