I know it's a little early but I have already started developing a website with the current v7.2 nightly which includes the new document type composition feature. Have you thought about how uSync will work with compositions yet?
Yeah - I've been looking at it - It shouldn't be two big a deal to add to the import and export process - at the moment I am still holding back - the last nightly i got didn't install properly : ) I will probably re-visit it in a week or two.
The latest release works with 7.2 - as the composition support was put into the core API before release. So no uSync changes needed to make it work :-)
I'm not sure how related this is, but I was just having issues doctype syncing. I was getting the following error:
2015-01-06 14:14:04,153 [26] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 1] An unhandled exception occurred System.NullReferenceException: Object reference not set to an instance of an object. at jumps.umbraco.usync.uSync.RunSync() at jumps.umbraco.usync.uSync.DoOnStart() at jumps.umbraco.usync.uSync.OnApplicationStarted(UmbracoApplicationBase httpApplication, ApplicationContext applicationContext) at Umbraco.Core.CoreBootManager.<Complete>b__5(IApplicationEventHandler x) at Umbraco.Core.EnumerableExtensions.ForEach[TItem](IEnumerable`1 items, Action`1 action) at Umbraco.Core.CoreBootManager.Complete(Action`1 afterComplete) at Umbraco.Web.WebBootManager.Complete(Action`1 afterComplete) at Umbraco.Core.UmbracoApplicationBase.StartApplication(Object sender, EventArgs e) at Umbraco.Core.UmbracoApplicationBase.Application_Start(Object sender, EventArgs e)
I took all the doctypes that depended on a composition out of the uSync folder and reloaded. That worked, so I added back in the types that depended on them and that worked. Could be something with the order doctypes are created?
I had to rename my Composition Aliases to get this to work with the latest version.
If you have a composition that starts with the letter S (like SEO) and you have a Doc Type that uses it (like Appelation), then the import from uSync fails as the SEO doctype does not exist when uSync tries to create the Appelation Doc Type. Renaming the alias of the SEO doctype to aaSEO and re-exporting via uSync makes the import work.
I've had some time to look at this now, and Its down to the order in which uSync imports the doctypes - with composites you have to ensure all teh composite types are in before you put any dependent types in.
So i've poked around the Umbraco source and aquired a better sort for usync
I've released an update 2.4.9 - that does the sorting before import, so it now does this better.
Umbraco v7.2 doc type composition support
I know it's a little early but I have already started developing a website with the current v7.2 nightly which includes the new document type composition feature. Have you thought about how uSync will work with compositions yet?
Yeah - I've been looking at it - It shouldn't be two big a deal to add to the import and export process - at the moment I am still holding back - the last nightly i got didn't install properly : ) I will probably re-visit it in a week or two.
Cool! The current nightlies are pretty stable and I think very close to a beta release now ;)
OK, the latest uSync 'nightly' supports Composition
https://github.com/KevinJump/jumps.umbraco.usync/tree/v2.x-Umbraco7.2/Package/uSync
if you already have usync 2.2 installed you only need to update jumps.umbraco.usync.dll
At some point the core exports will probably start to support composition too, and then the names might mismatch. but for now it works.
Wow, that's super awesome! Thanks Kevin!
Is this merged into the release yet?
would also be interested to hear if this is in the release?
The latest release works with 7.2 - as the composition support was put into the core API before release. So no uSync changes needed to make it work :-)
Great, thanks Kevin
I'm not sure how related this is, but I was just having issues doctype syncing. I was getting the following error:
I took all the doctypes that depended on a composition out of the uSync folder and reloaded. That worked, so I added back in the types that depended on them and that worked. Could be something with the order doctypes are created?
Hope this makes sense.
I had to rename my Composition Aliases to get this to work with the latest version.
If you have a composition that starts with the letter S (like SEO) and you have a Doc Type that uses it (like Appelation), then the import from uSync fails as the SEO doctype does not exist when uSync tries to create the Appelation Doc Type. Renaming the alias of the SEO doctype to aaSEO and re-exporting via uSync makes the import work.
Regards,
Matt
Hi,
I've had some time to look at this now, and Its down to the order in which uSync imports the doctypes - with composites you have to ensure all teh composite types are in before you put any dependent types in.
So i've poked around the Umbraco source and aquired a better sort for usync
I've released an update 2.4.9 - that does the sorting before import, so it now does this better.
That's awesome Kevin, I have noticed this issue but didn't have time to work out exactly what the cause was yet!
is working on a reply...