I want to export only the changed items like document types or content by selecting the individuals to the UAT from Dev environment instead of entire export.
And what is the way to roll back my changes from UAT using uSync.
Exporter can't really tell what the changes are between environments as it only knows about the local site.
Publisher can tell - when it does the push and pull it is doing the comparisons between environments and only the changes get pushed from one to the other - so this sort of has the same effect as what you are asking for, except it all happens in one process.
Publisher exports everything from a tree locally, then passes it over to the target site where it is compared and then only the changes are kept. when you then say "apply" to those changes, those are the files that are applied.
but It doesn't give you a zip of the changes or anything.
At the moment rollback via uSync isn't really something that you can do (other than reverting source control and reapplying what was there).
It can be something we can look into, we had something similar many versions ago, but mostly it was unused, and caused secondary problems
(you can't for example just rolls back a doctype, because when you change a doctype, all published content using it is also changed, so the rollback has to know about that too or you might lose content)
Is there any way to export only the changed items instead of all items in uSync Export
I want to export only the changed items like document types or content by selecting the individuals to the UAT from Dev environment instead of entire export.
And what is the way to roll back my changes from UAT using uSync.
Hi,
Exporter can't really tell what the changes are between environments as it only knows about the local site.
Publisher can tell - when it does the push and pull it is doing the comparisons between environments and only the changes get pushed from one to the other - so this sort of has the same effect as what you are asking for, except it all happens in one process.
Publisher exports everything from a tree locally, then passes it over to the target site where it is compared and then only the changes are kept. when you then say "apply" to those changes, those are the files that are applied.
but It doesn't give you a zip of the changes or anything.
At the moment rollback via uSync isn't really something that you can do (other than reverting source control and reapplying what was there).
It can be something we can look into, we had something similar many versions ago, but mostly it was unused, and caused secondary problems (you can't for example just rolls back a doctype, because when you change a doctype, all published content using it is also changed, so the rollback has to know about that too or you might lose content)
Im using a manual rollback - first I copy the data from production before I uploade the usync files.
If I have to make a rollback I have the backup.
is working on a reply...