yeah it looks like the package actions documentation went missing when the our.umbaco site was updated. :(
i don't think there is much appetite to redo the documentation because the road-map is to redo/maybe remove package actions in upcoming versions, and move to Migrations . (see https://cultiv.nl/blog/using-umbraco-migrations-to-deploy-changes/) - because they can also be used when deploying via nuget, and i think that is the direction things are going.
that said the best place for documentation now is probibly the umbraco source code
package actions are built from any class that impliments IPackageAction so searching the repo for those classes will show you the action classes
Thanks for sharing that great experience on the issue. Better to wait for the new .NET approach, and some more documentation, than start learning the old action-based then.
We want to create a package that is deployed via nuget but that contains document types and data types and templates.
We can't work out any way of making this work without deploying individual uSync files and manually importing these after bringing the package over in nuget. Is there a way of combining nuget for distribution and Umbraco Package for the actual installation? I presume not?
Is there a plan to support adding doctypes and such via migrations? Perhaps this is already possible as a hack by writing c# code to create doctypes in the Migrations?
yep - at the moment there is no inbuilt way to bring the doctypes of datatypes across as part of a migration,
but you could use the packageService (ApplicationContext.Services.PackageService) to do imports - this is what is called by the package installer to do it. so it will give you the same results.
you will need to feed it the xml elements, and it will do the imports.
however when you are doing complex mapped things these services won't always give you the exact result you might expect (so for example if you have a multinode tree picker datatype - with a starting root node, that won't be mapped as part of the import)
but for first time creation of things they should work ok.
Package documentation gone?
Hi there.
If I click on "Package actions documentation" in Developer > Packages > Package Actions I am sent to a 404:
https://our.umbraco.org/wiki/reference/packaging/package-actions
Anyone know where the documentation has been moved to?
Hi
yeah it looks like the package actions documentation went missing when the our.umbaco site was updated. :(
i don't think there is much appetite to redo the documentation because the road-map is to redo/maybe remove package actions in upcoming versions, and move to Migrations . (see https://cultiv.nl/blog/using-umbraco-migrations-to-deploy-changes/) - because they can also be used when deploying via nuget, and i think that is the direction things are going.
that said the best place for documentation now is probibly the umbraco source code
package actions are built from any class that impliments IPackageAction so searching the repo for those classes will show you the action classes
https://github.com/umbraco/Umbraco-CMS/search?l=C%23&q=IPackageAction&utf8=%E2%9C%93
and quite often the comments in those classes show the example usage for the action
https://github.com/umbraco/Umbraco-CMS/blob/dev-v7/src/umbraco.cms/businesslogic/Packager/PackageActions/addDashboardSection.cs
Thanks for sharing that great experience on the issue. Better to wait for the new .NET approach, and some more documentation, than start learning the old action-based then.
I was also trying to find documentation on this.
We want to create a package that is deployed via nuget but that contains document types and data types and templates.
We can't work out any way of making this work without deploying individual uSync files and manually importing these after bringing the package over in nuget. Is there a way of combining nuget for distribution and Umbraco Package for the actual installation? I presume not?
Is there a plan to support adding doctypes and such via migrations? Perhaps this is already possible as a hack by writing c# code to create doctypes in the Migrations?
yep - at the moment there is no inbuilt way to bring the doctypes of datatypes across as part of a migration,
but you could use the packageService (ApplicationContext.Services.PackageService) to do imports - this is what is called by the package installer to do it. so it will give you the same results.
you will need to feed it the xml elements, and it will do the imports.
however when you are doing complex mapped things these services won't always give you the exact result you might expect (so for example if you have a multinode tree picker datatype - with a starting root node, that won't be mapped as part of the import)
but for first time creation of things they should work ok.
Note: If it should be in anyones interest, I found the documentation at waybackmachine, just for reference:
https://web.archive.org/web/20140805045700/http://our.umbraco.org/wiki/reference/packaging/package-actions
is working on a reply...