Can you try and parse the additional parameter -rootPublication "000 YOUR ROOT PUBLICATION" (similar to your Blueprint). The default root and master publications are 000 Empty and 100 Master. You above command does not include this parameter. Try it out in a test publication before doing the acutal installation.
Possible values for cms-import are documented here.
Update:
Your question was unclear indeed! There is no straight forward way to accomplish any customization, apart from the ones already mentioned in the online documentation. The master-only pretty much gives you only the templates and schemas that are needed in the master level.
You can create your own custom installation package with any exclusions but you will have to carry the prophecy forward for future updates and maintenance. I would not recommend something of this nature but if you would like to proceed, you may have a couple of options.
Option 1
- Run the default MASTER ONLY installer in DEV or a VM
- Login to CME and remove the items that you don't intend to use in your
blueprint or higher environments.
- Create a new content porter
package and import your custom packages to all environments.
Option 2 ( an improvisation on 1)
Run the default MASTER ONLY installer in DEV or a VM
Login to CME and remove the items that you don't intend to use in
your blueprint or higher environments.
Create a new content porter package
- Modify the import script with your custom import package
$importPackageFullPath = Join-Path $PSScriptDir
("YOUR_CUSTOM_-master-only.zip")
- Use your custom installation to install in all environments with your custom content porter package.
Like I said earlier, you will have to carry this forward for future upgrades. So unless there is a dire need for it, I would advice against doing something of the above nature.
