Forum


HomeHomePremiumPremiumSkinningSkinningCreating a new skin packageCreating a new skin package
Previous
 
Next
New Post
11/13/2017 4:28 AM
 

Hi Aderson,

Just elaborating a little bit.

I've created a new skin by copying the Xcillion directories within the skins and container directories.

I then changed and added some files to create a 'new' skin. But the 'new'  skin doesn't show up in the list of skins available for the package.

So as you mentioned I could give it a name, I thought to create a skin package from the Xcillion skin and rename it, then reapply the changes but that's not going to work I think.

Is it possible to register the new directories as a skin using the 'create new extension button' at 'Host/Extensions'?

Best Regards,

Steve

 
New Post
11/13/2017 11:22 AM
 

Hi Steve,

1 - If you are using DNN 8 during the "Create Package" wizard when it says "Create Manifest" with the entire manifest XML displayed in the text box you should change the following entries:

- package name
- friendlyName
- skinName
- basePath

with the new name you want.

2 - Also you should rename on the following step these 2 fields
- Manifest File Name:
- Archive File Name:

That worked for me and at the end I had the new zip under "[root]\Install\Skin"

Cheers,

Aderson

 
New Post
11/13/2017 12:12 PM
 

Hi Aderson,

Thank you for your reply.

OK I'm with it now, I thought somehow I should be able to rename the skin by changing one field somewhere :-)

I am using DNN 8 by the way.

So I've created a new renamed theme based on the Xcillion theme. It installs OK but there are a couple of issues.
First, I get a warning:
"If you have reached this page it is because the installer needs to gather some more information before proceeding.
The package contains files with invalid File Extensions (map, woff2, manifest)
The installer maintains a list of allowable files (whitelist) that can be installed into the site. If you are confident that the package you are installing is from a reliable source then you can elect to ignore this list."

I'm not sure how to get rid of that.

Secondly, the Container files are not included. I can see there's a list of included files for the skin in the manifest, presumably, I need to create an equivalent list for the container files somehow.

Best Regards,

Steve

 

 
New Post
11/14/2017 8:57 AM
 

Hi Steve,

1 - In terms of the message, not much can be done. These are files that are NOT authorized by default by dnn and you will get that warning if a file inside has an extension which is not authorized by DNN.

2 - It seems that you have to follow a similar process by this time for the container package.

Cheers,

Aderson

 
New Post
11/14/2017 9:10 AM
 
Hi Aderson,

Thank you for your reply.

I suspect those files are not necessary for my purposes, so I will look at removing them.

I'd always assumed skins/themes and container would install together, a separate container package is a minor inconvenience. But if I can generate the container package then look and see if the two can be combined. If that's possible.


Thank you once again.

Steve
 
Previous
 
Next
HomeHomePremiumPremiumSkinningSkinningCreating a new skin packageCreating a new skin package



Try FREE
30 days money back guaranteed