The way uSync attaches to events is slightly diffrent in 6. so you need to use the version 6 package for umbraco 6. installs
2. Versioning
uSync will now save a version of each change you make to a document type, stylesheet, template or macro when you save it inside umbraco. the files are stored in the archive folder (~/uSync.Archive by default) with a date timestamp on them.
versioning can be turned off via the config (versions="false")
because DataTypes are not dynamically saved, you get a new version every application start.
uSync is an amazingly simple yet powerful package. Thanks for making it! We're starting to use it right now.
Regarding the 3 issues above... Can I request that you work first on Media Types. That would make the package a more whole solution.
I think the data type issue is an Umbraco limitation and you shouldnt pull your hair out trying to fix it. The issue may be fixed by Umbraco in the near future anyway. And the "installing twice" issue...well IMO that's the fault of the developer. It's an edge-case of developer error :)
ps. Are you planning on doing dictionary items too?
Yes Media Types are next. but as the core doesn't have the XML functions (notice media types missing from packages?) I'm having to actually think - taking a bit longer.
I am aiming for v1.0 doing everything that can be saved out of hte DB so Dicitonary types and Relations (what ever they are :) )
I think for media types you could duplicate the doctype xml structure for the purpose of saving to file. Don't worry about Umbraco limitations, just work around them :)
And yes, wtf are relations?
Why not leave relations as a 1.1 release. Seriously I only know 2 people who use them.
IMO, Media Types bring the most value to your package. BTW, when will these be done? I'm eager to add this to our automated processes.
@Mr Dang - We are using relations on nearly every site we build! ;) Makes querying related date nice and quick, rather than iterating through everything to find the things you want. Horse for courses! ;)
uSync 0.91 beta ! has been uploaded and includes MediaTypes (i think!) - if you already have an install you can just copy the dll in the package over the top.
I have tested it a bit on 4.11.4 - it seems to be working, although at one point i corrupted the cached (deleteing folderes App_Data/TEMP fixed that)
Going to do some more testing, and i think move the settings from web.config to uSync.config in umbraco folder. less risky that way.
Yes i might do relations for v1 (seems we're using them :) )
Yeah we only use them with the multinode picker to record where something is 'picked from' in the opposite direction; inspired by the 24days post before christmas: http://24days.in/umbraco/2012/who-picked-this/
but I sense they can be used for more, where the relationship between nodes isn't obvious, or to avoid traversing the whole tree, for performance reasons
maybe if you were writing a blog package, and someone 'comments on a post', you could at this point, create an additional relation directly between the commenter and the post, using the relations api, which then if you wanted to have a list of all the posts that person had commented on, it would save you having to loop through all the comments on the blog, filtering out the ones by the particular person, and building a list of commented on posts, you would instead just query the defined 'postscommentedonby' 1-1 relation between the member and the post, direct... uPostysICommentsysOnsy ?? :-P
uSync - Release Notes 0.9
Version 0.9 has two new things
1. A Umbraco 6 version of uSync.
The way uSync attaches to events is slightly diffrent in 6. so you need to use the version 6 package for umbraco 6. installs
2. Versioning
uSync will now save a version of each change you make to a document type, stylesheet, template or macro when you save it inside umbraco. the files are stored in the archive folder (~/uSync.Archive by default) with a date timestamp on them.
versioning can be turned off via the config (versions="false")
because DataTypes are not dynamically saved, you get a new version every application start.
Known Issues
1 DataTypes still don't save when you click save inside Umbraco, this appears to be a bug in events for DataTypes - http://issues.umbraco.org/issue/U4-1781
2. Media Types not included : I'm working on this, my last attempt was a YSOD on every save. when this is done it might make v1.0
3. Installing uSync twice will cause you a YSOD - because it will add itself to your web.config twice.
uSync is an amazingly simple yet powerful package. Thanks for making it! We're starting to use it right now.
Regarding the 3 issues above... Can I request that you work first on Media Types. That would make the package a more whole solution.
I think the data type issue is an Umbraco limitation and you shouldnt pull your hair out trying to fix it. The issue may be fixed by Umbraco in the near future anyway. And the "installing twice" issue...well IMO that's the fault of the developer. It's an edge-case of developer error :)
ps. Are you planning on doing dictionary items too?
Yes Media Types are next. but as the core doesn't have the XML functions (notice media types missing from packages?) I'm having to actually think - taking a bit longer.
I am aiming for v1.0 doing everything that can be saved out of hte DB so Dicitonary types and Relations (what ever they are :) )
I think for media types you could duplicate the doctype xml structure for the purpose of saving to file. Don't worry about Umbraco limitations, just work around them :)
And yes, wtf are relations?
Why not leave relations as a 1.1 release. Seriously I only know 2 people who use them.
IMO, Media Types bring the most value to your package. BTW, when will these be done? I'm eager to add this to our automated processes.
Sorry working to Open Source timescales .... Soon :)
hopeing to get it working this week - i started duplicating DocType code from the installer, (it's in the source https://github.com/KevinJump/jumps.umbraco.usync/blob/master/jumps.umbraco.usync/SyncMediaTypes.cs) suspect it's just doing one thing diffrently.
@Mr Dang - We are using relations on nearly every site we build! ;) Makes querying related date nice and quick, rather than iterating through everything to find the things you want. Horse for courses! ;)
LG you're one of the 2 people I was talking about :)
The other would be Hendy :)
Umm Kev, you do know we're using Relations on the current liverpool.gov migration you are overseeing... :-)
uSync 0.91 beta ! has been uploaded and includes MediaTypes (i think!) - if you already have an install you can just copy the dll in the package over the top.
I have tested it a bit on 4.11.4 - it seems to be working, although at one point i corrupted the cached (deleteing folderes App_Data/TEMP fixed that)
Going to do some more testing, and i think move the settings from web.config to uSync.config in umbraco folder. less risky that way.
Yes i might do relations for v1 (seems we're using them :) )
@Anthony - sounds like you're missing out :p
Yeah all the cool kids are using relations. Everyone else doesnt know what they are :/
relations which you can mimic with mntp which is why i havent used them i think i need to investigate further
Yeah we only use them with the multinode picker to record where something is 'picked from' in the opposite direction; inspired by the 24days post before christmas: http://24days.in/umbraco/2012/who-picked-this/
but I sense they can be used for more, where the relationship between nodes isn't obvious, or to avoid traversing the whole tree, for performance reasons
maybe if you were writing a blog package, and someone 'comments on a post', you could at this point, create an additional relation directly between the commenter and the post, using the relations api, which then if you wanted to have a list of all the posts that person had commented on, it would save you having to loop through all the comments on the blog, filtering out the ones by the particular person, and building a list of commented on posts, you would instead just query the defined 'postscommentedonby' 1-1 relation between the member and the post, direct... uPostysICommentsysOnsy ?? :-P
that's my trade mark :)
btw it's uCommentsy
is working on a reply...