012b43a1c2
* make CoreScopeProvider available for derived classes * Create publish controller * Add publish functionality * Remove unneeded using * Implement publish for multiple cultures * support multiple cultures in controler * Dont validate properties * Refactor to use PublishingOperationStatus * refactor to use proper publish async methods * Refactor publish logic into own service * Commit some demo code * Add notes about what errors can happen when publishing * Rework ContentPublishingService and introduce explicit Publish and PublishBranch methods in ContentService * Fix merge * Allow the publishing strategy to do its job * Improved check for unsaved changes * Make the old content controller work (as best possible) * Remove SaveAndPublish (SaveAndPublishBranch) from all tests * Proper guards for invalid cultures when publishing * Fix edge cases for property validation and content unpublishing + add unpublishing to ContentPublishingService * Clear out a few TODOs - we'll accept the behavior for now * Unpublish controller * Fix merge * Fix branch publish notifications * Added extra test for publishing unpublished cultures and added FIXME comments for when we fix the state of published cultures in content --------- Co-authored-by: Nikolaj Geisle <70372949+Zeegaan@users.noreply.github.com> Co-authored-by: Zeegaan <nge@umbraco.dk>
Umbraco Test Data
This project is a utility to be able to generate large amounts of content and media in an Umbraco installation for testing.
Usage
You must use SQL Server for this, using SQLCE will die if you try to bulk create huge amounts of data.
It has to be enabled by an appSetting:
{
"Umbraco": {
"CMS": {
"TestData": {
"Enabled" : true,
}
}
}
}
Once this is enabled this endpoint can be executed:
/umbraco/surface/umbracotestdata/CreateTree?count=100&depth=5
The query string options are:
count= the number of content and media nodes to createdepth= how deep the trees created will belocale(optional, default = "en") = the language that the data will be generated in
This creates a content and associated media tree (hierarchy). Each content item created is associated to a media item via a media picker and therefore a relation is created between the two. Each content and media tree created have the same root node name so it's easy to know which content branch relates to which media branch.
All values are generated using the very handy Bogus package.
Schema
This will install some schema items:
umbTestDataContentDocument Type. TIP: If you want to delete all of the content data generated with this tool, just delete this content typeUmbracoTestDataContent.RTEData TypeUmbracoTestDataContent.MediaPickerData TypeUmbracoTestDataContent.TextData Type
For media, the normal folder and image is used
Media
This does not upload physical files, it just uses a randomized online image as the umbracoFile value.
This works when viewing the media item in the media section and the image will show up and with recent changes this will also work
when editing content to view the thumbnail for the picked media.