Yes you can do it, but when going between v6 and v7 you will hit quite a few other issues espeically around datatypes.
uSync will migrate datatypes and anything based on the core datatypes (so textbox, rich text editor, drop downs...) should come accross ok, but things outside of that like uComponents, DAMP media pickers etc, don't have a direct migration path - for many datatypes there isn't an equivalent from v6 to v7 and where there is most of them now store their information in a different format in v7 from v6.
But if all the data types (or new ones) are OK or replaced then uSync will migrate all the other stuff so
Document Types <-- need the datatypes to be there, or uSync won't be
able to create the properties.
Stylesheets
Templates
Dictionary Items
Macros
Languages
Also if you then want to migrate the content uSync.ContentEdition will do this, but a lot of the content data will probably have changed format (again depending on the datatypes used). If you are moving everything i would say it makes more sense to follow the upgrade path of umbraco.
I'm exploring all my options for the current upgrade/development will be in 6.2 but I want to test in version 7.2 so the development I do now I'll be able to port in the future.
Secondly what will happen with a unknown datatype will it be created as a readonly ?
I don't think uSync will create it as a readonly. uSync doesn't do any of attempted the mapping that the upgrade does, so if it can't find the underlying type it will not import it, and then just put something in the log file.
You can however do that by hand and turn any imported type into readonly, by just changing the ID in the usync *.config file to Id="Umbraco.NoEdit" before you run the import.
but I would be inclined to try that with uSync 2.5 on 7.3.
Even if it's though the latest version - usync 2.5 should still work getting files out of 7.3 and then the layout and possibly format will be closer. to that used by the v6 versions.
uSync between V6.2 and V7.2
Hi
Quick question.
Is it possible to use usync between major versions of Umbraco?
Regards
Hi,
Yes you can do it, but when going between v6 and v7 you will hit quite a few other issues espeically around datatypes.
uSync will migrate datatypes and anything based on the core datatypes (so textbox, rich text editor, drop downs...) should come accross ok, but things outside of that like uComponents, DAMP media pickers etc, don't have a direct migration path - for many datatypes there isn't an equivalent from v6 to v7 and where there is most of them now store their information in a different format in v7 from v6.
But if all the data types (or new ones) are OK or replaced then uSync will migrate all the other stuff so
Also if you then want to migrate the content uSync.ContentEdition will do this, but a lot of the content data will probably have changed format (again depending on the datatypes used). If you are moving everything i would say it makes more sense to follow the upgrade path of umbraco.
Thank You
I'm exploring all my options for the current upgrade/development will be in 6.2 but I want to test in version 7.2 so the development I do now I'll be able to port in the future.
Secondly what will happen with a unknown datatype will it be created as a readonly ?
Regards
Hi,
I don't think uSync will create it as a readonly. uSync doesn't do any of attempted the mapping that the upgrade does, so if it can't find the underlying type it will not import it, and then just put something in the log file.
You can however do that by hand and turn any imported type into readonly, by just changing the ID in the usync *.config file to
Id="Umbraco.NoEdit"before you run the import.Brilliant. Thanks for your input
Would the other way around work as well? From 7.3.x to the latest 6.x?
In theory :)
but I would be inclined to try that with uSync 2.5 on 7.3.
Even if it's though the latest version - usync 2.5 should still work getting files out of 7.3 and then the layout and possibly format will be closer. to that used by the v6 versions.
is working on a reply...