Creation of dummy content

[hardyjames86]

Hi all, i am using articulate version 5.0.0.
I have migrated this to umbraco cloud version 13.
I have a problem where every time i clone down umbraco cloud project to work on locally and run it for the first time, Articulate creates an Articulate node in the content tree and adds dummy articles.
When this happens it creates new uda files causing schema mismatch untill they are committed and pushed to source control to be deployed on cloud.
Is there anyway to stop the creation of this dummy content in the content tree?

Thanks :)

[Shazwazza]

Hi, would need some investigation into Umbraco for that. The content population is done via the normal Umbraco packaging system. IIRC, the packaging system works by adding a row to the DB to indicate that a package is installed. If that row doesn't exist, then it thinks the package is not installed and will proceed with installation. Perhaps there is a way to turn off auto-package installation and only rely on it to manually be triggered in the back office.

[protherj]

I'm also seeing this. I clone fresh on a new machine and I get a collision. When I login to the Umbraco back-office, there is dummy Articulate content and only the Articulate DocTypes. I believe this creation is happening before the Cloud Restore can happen.

Is there a way to disable the initial dummy data and DocType creation?

I'll see if I can get around this be deleting everything and trying to restore again.

[hardyjames86]

Hi, thanks Shazwazza, sorry I just noticed your comment after I got a notification from the other comment outlining they had the same issue. I haven't worked on Umbraco cloud since, but, I do remember I got round the problem by changing a setting in the Umbraco cloud deploy config. It's been a while and I don't have access to the project unfortunately

[protherj]

Yea, deleting the content, DocTypes, and Data Types added by Articulate, then revert the repo back to align with the "main" branch allowed the initial deploy to finish at the restore could start.

[hardyjames86]

great, appologies for the lack of clarity as it was a while ago now but i think i did something similar and set a flag in the umbraco-cloud.json file then there was no issue when transferring and restoring the schema/content between environments.

this could be wrong but it could have been the IgnoreBrokenDependenciesBehavior setting below

{
...
"Umbraco": {
"Deploy": {
"Settings": {
"ApiKey": "",
"ApiSecret": "",
"Edition": "Default",
"ExcludedEntityTypes": [],
"RelationTypes" : [],
"ValueConnectors": [],
"SessionTimeout": "0.0:20:00",
"SourceDeployTimeout": "0.0:20:00",
"DatabaseCommandTimeout": "0.0:20:00",
"EnableSignatureCacheReads": true,
"HttpClientTimeout": "0.0:20:00",
"DiskOperationsTimeout": "0.0:05:00",
"SourceDeployBatchSize": null,
"PackageBatchSize": null,
"MaxRequestLength": null,
"UseDatabaseBackedTransferQueue": true,
### "IgnoreBrokenDependenciesBehavior": "Restore",
"AcceptInvalidCertificates": false,
"TransferFormsAsContent": true,
"TransferDictionaryAsContent": false,
"IgnoreMissingLanguagesForDictionaryItems": false,
"SetEmptyDictionaryItemsOnTransfer": true,
"AllowMembersDeploymentOperations": "None",
"TransferMemberGroupsAsContent": false,
"ExportMemberGroups": true,
"ReloadMemoryCacheFollowingDiskReadOperation": false,
"AllowDomainsDeploymentOperations": "None",
"AllowWebhooksDeploymentOperations": "None",
"TrashedContentDeploymentOperations": "Import",
"PreferLocalDbConnectionString": false,
"MediaFileChecksumCalculationMethod": "PartialFileContents",
"NumberOfSignaturesToUseAllRelationCache": 100,
"ContinueOnMediaFilePathTooLongException": false,
"SuppressCacheRefresherNotifications": false,
"ResolveUserInTargetEnvironment": false,
"Suspensions": {
"DiskRead": "All",
"PartialRestore": "All",
"Restore": "All",
"Deploy": "All",
"Import": "All",
"Export": "All"
},
"HideConfigurationDetails": false,
"HideVersionDetails": false
}
}
}
}