My goal is to export only certain container nodes, but not their actual children. This would allow the Content Picker editor to have the "Starting Node" property set in the Development environment and remain consistent throughout all other environments.
I'm new to using Content Edition, so thanks for your help!
I figured it out, if anyone else wants to accomplished something similar.
I made a copy of the the ContentHandler class from uSync source code and added it to my Umbraco web project.
Only exports items with a content type alias that ends with Repo, such as componentRepo, menuRepo, pageHeaderRepo, etc. Requires a root item of type Repo. There is probably a better way to do this, but this works perfectly for my needs.
And I can't implement the solution posted by James either. There is no GetExportItems method to override. Should I instead override the ShouldExport and/or ShouldImport methods? Or is there another solution?
I've disabled all other handlers except the content one. and I want uSync to ignore exporting anything from the /Partners node.
However, each time I perform an export, the content from the /Partners node get's exported.
I've tried with "/Partners", "/Partners/", "/Partners/*" and even "/Partners/DevInstallatoren" (which is one specific piece of content under that node.
uSync Content Manager v8 ignore settings not working
The config file appears to be different in v8. How do we make Content Edition ignore items?
Above is an attempt to ignore the root Home page. I've tried several things, but the home.config file always writes to disk.
Thanks!
Or better yet, can Content Edition be configured to only export certain Document Types in v8?
Similar to this? Issue with exporting content
My goal is to export only certain container nodes, but not their actual children. This would allow the Content Picker editor to have the "Starting Node" property set in the Development environment and remain consistent throughout all other environments.
I'm new to using Content Edition, so thanks for your help!
Anyone have a suggestion or example?
I'd really like to export content based on its name and or some common property.
I have not found a complete working example of how to extend uSync content edition and the docs appear to be related to older versions.
I figured it out, if anyone else wants to accomplished something similar. I made a copy of the the ContentHandler class from uSync source code and added it to my Umbraco web project.
Altered the SyncHandler attributes:
Renamed the Class to RepoContentHander and added the following override :
Only exports items with a content type alias that ends with Repo, such as componentRepo, menuRepo, pageHeaderRepo, etc. Requires a root item of type Repo. There is probably a better way to do this, but this works perfectly for my needs.
As pointed out editing the config like this doesn't appear to work.
And I can't implement the solution posted by James either. There is no GetExportItems method to override. Should I instead override the ShouldExport and/or ShouldImport methods? Or is there another solution?
Hi ,
for v8.4 we've added the settings back into uSync
https://jumoo.co.uk/usync/docs/v8/contentEdition/contentHandler/
something like this should now work.
This does not work, there is my relevant config section:
I've disabled all other handlers except the content one. and I want uSync to ignore exporting anything from the /Partners node. However, each time I perform an export, the content from the /Partners node get's exported.
I've tried with "/Partners", "/Partners/", "/Partners/*" and even "/Partners/DevInstallatoren" (which is one specific piece of content under that node.
But alas, nothing works. Please advise!
Yeah, sorry stupid error in the code for that one 😥
patch update (8.5.1.1) for uSync.ContentEdition fixes it.
see : https://www.nuget.org/packages/uSync.ContentEdition/8.5.1.1
Issue (now closed) : https://github.com/KevinJump/uSync8/issues/87
It works as intended now! Thank you for the quick response!
thanks a lot for the quick response King!
LOL, Reported June 2019, I'd hate to see slow response.
LOL indeed, I just noticed when this post was originally created. I guess we were just lucky that Kevin was around when we posted
is working on a reply...