Hi Kevin, finding uSync really helpful, and uSync Content looks really intriguing too - but wondering if you are considering adding the ability to only read/write a particular area of the content tree, e.g. specifiy a start node?James.
It is possible in the code - but it would have to be more aware of where things like media items are used. at the moment the full content+media sync means it doesn't need to do dependency checking.
would you be thinking set a node id in a config and have it act as the new root for syncing? - or are you more in the Courier, pick something from the interface and package it up world?
What's missing really is a nice dashboard UI for these things to be called through. maybe it's my excuse to do some Angular JS on Umbraco 7 :)
From my point of view, a node id in the config file would be a brilliant starting point, and really would meet my immediate requirements. Would it need to do media dependency checking - I'd be happy doing it manually. Part of the appeal of uSync is the simplicity (and the not unrelated fact that it actually works!)
But a nice UI is always fun to have & I wouldn't want to deprive you of a Angular JS session!
FEATURE REQUEST: specifiy part of the content tree
Hi Kevin, finding uSync really helpful, and uSync Content looks really intriguing too - but wondering if you are considering adding the ability to only read/write a particular area of the content tree, e.g. specifiy a start node?James.
its not on the (admittedly non-existent) list
It is possible in the code - but it would have to be more aware of where things like media items are used. at the moment the full content+media sync means it doesn't need to do dependency checking.
would you be thinking set a node id in a config and have it act as the new root for syncing? - or are you more in the Courier, pick something from the interface and package it up world?
What's missing really is a nice dashboard UI for these things to be called through. maybe it's my excuse to do some Angular JS on Umbraco 7 :)
From my point of view, a node id in the config file would be a brilliant starting point, and really would meet my immediate requirements. Would it need to do media dependency checking - I'd be happy doing it manually. Part of the appeal of uSync is the simplicity (and the not unrelated fact that it actually works!)
But a nice UI is always fun to have & I wouldn't want to deprive you of a Angular JS session!
is working on a reply...