The code in 2.1.2-beta is as close to a working version as you can get right now. It should match the 3.0.0 branch of uSiteBuilder as I compiled it from that the other day (unless I screwed something up), can you let me know why you think it's different?
The "Don't install on 6.0.1 thread" was started as tab / propertyTypeGroup changes in 6.0.1 broke uSiteBuilder (and therefore the admin package), in fact they broke Umbraco itself (hence the patch releases) - I think the bulk of those problems have been solved now.
The v6 port thread started as discussing moving over to the new v6 APIs, but the priority should be getting a stable build for v6 before doing that. The discussion then veered off into maybe just working on something in the core instead, but post-CodeGarden we're back to working on fixing uSiteBuilder instead.
I've not used v6 in production, for the very reason that there might have been packages that weren't v6 ready (like this one), so I've not had the opportunity to use uSiteBuilder in anger on a v6 site.
General consensus about using uSiteBuilderAdmin / uSiteBuilderAdmin and V6.1.x?
I'm a little confused to what is happening with uSiteBuilderAdmin / uSiteBuilder and v6.1.x
Over here there is a thread that says Dont-install-on-umbraco-601-until-this-is-fixed and on the Google Groups there is talk of a v6 Port?
Also there is a uSiteBuilderAdmin_2.1.2-beta.zip, but this contains a different uSiteBuilder version than this branch here 3.0.0?
Is it ok to install the 2.1.2 beta and v6.1.x?
The code in 2.1.2-beta is as close to a working version as you can get right now. It should match the 3.0.0 branch of uSiteBuilder as I compiled it from that the other day (unless I screwed something up), can you let me know why you think it's different?
The "Don't install on 6.0.1 thread" was started as tab / propertyTypeGroup changes in 6.0.1 broke uSiteBuilder (and therefore the admin package), in fact they broke Umbraco itself (hence the patch releases) - I think the bulk of those problems have been solved now.
The v6 port thread started as discussing moving over to the new v6 APIs, but the priority should be getting a stable build for v6 before doing that. The discussion then veered off into maybe just working on something in the core instead, but post-CodeGarden we're back to working on fixing uSiteBuilder instead.
I've not used v6 in production, for the very reason that there might have been packages that weren't v6 ready (like this one), so I've not had the opportunity to use uSiteBuilder in anger on a v6 site.
Thanks Stephen, I was just enquiring because I was a little confused.
I've just installed 2.1.2-beta on V6.1.1 and I'll be trying it out with a (as yet) non-production site.
I have got to port a package i built to v6 so i will let you know how I get on.
I use v6 for all our new sites so would be good to have uSB back in the toolbox as i abandoned it after the issues i posted in the linked thread.
Fingers crossed! :)
My experience is that changes to existing doctypes won't sync using 2.1.2-beta.
Unfortunately there is no working Code First implementation for umbraco 6/7 as yet.
My money would be on waiting for the uSB redevelopment by Vega reported here: http://our.umbraco.org/projects/developer-tools/usitebuilder/usitebuilder-support/45666-uSiteBuilder-v2-a-rebuild
is working on a reply...