4

I'm currently trying to create a package version, but I'm encountering this error:

These entities are not supported: [Site]

The commands I used for creating a package and package version are the following:

# ~/Documents/Projects/public_sites

sfdx force:package:create --name public_sites --description "<desc_here>" --packagetype Unlocked --path force-app --targetdevhubusername ProductionOrg

sfdx force:package:version:create --package public_sites --installationkey <the_key> --wait 10 --targetdevhubusername ProductionOrg --definitionfile config/project-scratch-def.json

In the project-scratch-def.json file, I specifically added 2 features: PersonAccounts and Sites. Then in my force-app/main/default/sites I only have 1 site to deploy .site-meta.xml

​Any ideas are welcome.

Improve this question

1 Answer 1

Reset to default
5

The site is not packagable entity .You cannot package sites and hence the error .Try removing sites from the metadata folder that you package from.

Updates

You can see packageable metadata by going to https://yourOrgUrl/mdcoverage/report.jsp.

You can use .forceignore file to skip those that you don't want in metadata conversion

Improve this answer
3
  • 3
    Additionally, you can see packageable metadata by going to https://yourOrgUrl/mdcoverage/report.jsp. I find this incredibly useful for planning my unlocked packages.
    – John Towers
    Sep 7, 2018 at 1:50
  • That mdcoverage report is gold. Thank you @JohnTowers . In my opinion, I think it's not intuitive to not be able to package components that can be force:source:push/pull-ed. But if it's a limitation, then what can I do. In addition, thanks @Mohith for pointing to the right direction.
    – SamuelDev
    Sep 7, 2018 at 3:20
  • 2
    You can use .forceignore file to skip those that you don't want in metadata conversion
    – Mohith Shrivastava
    Sep 7, 2018 at 3:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .