Mike Chambers

That just checks that it is a json string though... and not that it is specifically json that is the correct schema for a mediaPicker3?

It's really difficult to translate as Areas in the new grid (aka old cells) don't have settings. (only way we've found to reimplement with the new areas is to have...

Getting this too.. The migrated config is below.. If it helps.. it does seem to relate to unpublished content. Some more info.. If I try to set the link and...

https://github.com/Shazwazza/Smidge/issues/91 `Also note that if file watching is enabled, this also affects cache busting. If watching is enabled then the actual cache bust value is a combination of the ICacheBuster...

So simple use case for file watcher and requiring cache busting on environments other than Development. Umbraco CMS, or any other CMS for that matter allows for backoffice editor updates...

That makes perfect sense, thank you for the swift response.

Pushing my luck.. so core migrators, are we talking https://cornehoskam.com/posts/how-to-create-run-migrations-umbraco-v10 and the https://docs.umbraco.com/umbraco-cms/extending/database#schema-class-and-migrations approach? rather than https://docs.umbraco.com/umbraco-cms/extending/packages/creating-a-package#package-migration

superstar! I presume I just loose the `run package migrations` bit and visibility in the back office? by it not being a package migration.. any thing else of note?

Definately pushing my luck now.. ;-) `[ComposeAfter(typeof(uSync.BackOffice.uSyncBackOfficeComposer))]` what happens if no uSync (optional) and not wanting to introduce a dependancy on uSync in my package?

So looks like things get done in the right order now at least according to the logs.. but that no notifications are raised from a `_dataTypeService.Save(dataType);` in a migration plan...