Professional DotNetNuke ASP.NET Portals wrox phần 10 pptx

Step 1

Log in with an Admin or Host account. If you are installing a skin for the current portal, go to the

Admin/Site Settings menu (see Figure 14-9). Skin files will be stored in the individual portal directory.

If multiple portals upload the same skin, then duplicate files will exist in the portal directories.

Figure 14-9

If you want all of the portals in a multi-portal installation to have access to the skin, make sure to log in

with the Host account and select the Host/Host Settings menu (see Figure 14-10).

Figure 14-10

375

Distribution

18_595636 ch14.qxd 5/10/05 9:55 PM Page 375

Step 2

Figures 14-11 and 14-12 show the key portions of the Portal Settings and Host Settings screens. Select the

Upload Skin link to go the File Upload screen.

Figure 14-11

Figure 14-12

Step 3

The File Upload screen provides a simple interface for uploading one or more skins (see Figure 14-13).

Browse to the desired skin package, click OK on the Browse dialog, and click the Add link on the File

Upload page. Use the Upload New File link button to finish installing the module.

Step 4

After installing a new skin package, you should review the upload logs (see Figure 14-14). Errors will be

highlighted in red. If no errors are shown, then the skin is ready for use in your portal. The location of

the installation directory will be displayed at the top of the logs. Note that the directory matches the

name of the skin package and will only vary based on whether the skin is installed from the Admin

menu or the Host menu.

376

Chapter 14

18_595636 ch14.qxd 5/10/05 9:55 PM Page 376

Figure 14-13

Figure 14-14

FTP-Based Installation

To install a new skin using FTP or any file manager, copy the module into the Install/Skin directory of

your DotNetNuke installation. When the ResourceInstaller task runs, it will install this skin using the

standard skin installation code. If an error occurs it will be noted in the task history, which is available

by selecting the History link for the ResourceInstaller task on the Schedule page (shown in Figure 14-7

previously).

377

Distribution

18_595636 ch14.qxd 5/10/05 9:55 PM Page 377

Containers

Containers, like skins, provide the ability to control the appearance of portal. While skins work at the

“page” level, containers are designed for wrapping individual modules that appear on the page. Each

module on a given page may use any one of the installed containers. Containers follow many of the

same packaging and installation processes as skins and differ primarily in the allowable content inside

the html or ascx definition files. Let’s take a look at these differences.

Packaging Containers

Containers follow all of the same packaging rules as skins. Container packages may contain files that are

applied to all container definition files in the package or that are specific to an individual container defi￾nition as outlined in Table 14-10. The behavior and purpose of these files is the same as for skins, and

only the names of the files are different.

Table 14-10: Container Filenames

File Type Global Name Individual Container Name

Configuration File Container.xml [container filename].xml

Style Sheet Container.css [container filename].css

Installing Containers

Containers follow the same procedures for web- and FTP-based installations. For web-based installa￾tions, in Step 2, select the Upload Container link instead of the skin link (shown in Figures 14-11 and

14-12 previously). Containers will be installed in the Portal or Host containers directory. To install con￾tainers using FTP, place the container package in the Install/Container directory.

Language Add-Ons

DotNetNuke 3.0 added support for multiple languages. The DotNetNuke implementation loosely fol￾lows the localization architecture and naming conventions of the upcoming ASP.NET 2.0 framework.

DotNetNuke 3.0 only recognizes a single type of language add-on: a Language Pack. This will likely

change in future DotNetNuke versions as the Language Pack is split into Core Language Packs and

Module Language packs.

Language Packs

The multi-language architecture poses a unique challenge for creating and installing Language Packs

due to the number of directories and files involved. Like code add-ons, Language Packs utilize a mani￾fest file to manage the meta-data necessary to get all of the files installed to the correct directory.

378

Chapter 14

18_595636 ch14.qxd 5/10/05 9:55 PM Page 378