DotNetNuke Skinning Whitepaper (skin upload part)

Skin Upload

Once the executable skin based on the ascx file format is added to the ASPX page, malicious script in some skin files can compromise the entire system. Based on this consideration, the host has a host or site to upload the skin of the authorization function. Log in with Host account, select Host settings under the Host column, you can see this option. If the option is set to Portal (default), then the site's administrator can upload their site's skin without interference from the host.

Any file upload function is concentrated in the DotNetNuke site management or host management of the file Management column. In the management of the Web site under the file management upload skin, this skin is only applicable to the site, and if the host management under the upload of skin is applicable to all sites of the host. The file Manager has an upload option, which appears to allow uploading of the file upload interface for skin and container packages. You should choose the appropriate file usage option before uploading the package (the application uses this to differentiate the compression package). Note: This option will not appear if you do not receive an upload authorization. ：（

The skin upload mechanism automatically compresses the skin package, creates the necessary folders and releases the file, and replaces the placeholder in the HTML file with the ASP.net script to convert the HTML file to an Ascx user control. This transformation is implemented according to the definition of the skin object in the Modulecontrols table in the database. Ascx user control files and CSS style sheet files still associate graphics files in a relative way. Note: If you upload a skin package that contains both skin and containers (Containers.zip and Skins.zip), you should select the Skin Pack option.