I have got a problem when I try to delete a doctype.
I have got 2 instances of umbraco project. When I create a doctype in the first instance and then copy an usync folder to the second instance it works fine. I can see my docype that was created in the first instance. But when I delete doctype and then copy the usync folder - the doctype is not deleted from the second instance.
I wonder if I all do right or maybe this functionality has not implemented yet?
Yes it isn't implemented within the package yet - the latest development branch in github has functionality to delete but its quite a leap.
In order to do deletes usync needs to track the unique ids of the datatypes on one install and map them across to any other install.
The dev branch is doing this via a set of local XML files placed in the temp folder .
These map the master (source) guid for a doctype to the local guid on each install. A usync actions file in the usync folder is then tracking deletes and renames of doctypes across installs.
This is how usync.contwntesition works for content so hopefully it will work well... But the amount of change means I want to test it a lot before updating the main package to it
Do I have to delete myself any files from the uSync folder? The other day, this scenario happened with me, where I had to delete a Document Type. Then after that, I noticed an exclamation mark in VS uSync folder for the file I deleted.
When I pushed changes to web, I got my deployment broken and had to delete everything and do a fresh new installation.
Also, I am not sure if you could help me out on this. I had established a web app on Azure together with a staging deployment slot.
I usually publish to staging, then I publish again to production (I don't make use of SWAP). However, for some reason, both were pointing to the same DB, despite the fact I changed the staging to point to staging DB. I solved this by making the staging use SQL Compact and the production use normal SQL. That sounds weird!
So back to the main topic, do I need to make any special configuration to make deletions work?
Deletion document type
Firstly - thanks for this package.
I use Umbraco1.6.5 and usync configuration
<usync read="true" write="false" attach="true" folder="~/uSync/" archive="~/uSync.Archive" versions="true" preserve="false">
I have got a problem when I try to delete a doctype.
I have got 2 instances of umbraco project. When I create a doctype in the first instance and then copy an usync folder to the second instance it works fine. I can see my docype that was created in the first instance. But when I delete doctype and then copy the usync folder - the doctype is not deleted from the second instance.
I wonder if I all do right or maybe this functionality has not implemented yet?
Any advices?
Thanks,Oleg
Hi
Yes it isn't implemented within the package yet - the latest development branch in github has functionality to delete but its quite a leap.
In order to do deletes usync needs to track the unique ids of the datatypes on one install and map them across to any other install.
The dev branch is doing this via a set of local XML files placed in the temp folder .
These map the master (source) guid for a doctype to the local guid on each install. A usync actions file in the usync folder is then tracking deletes and renames of doctypes across installs.
This is how usync.contwntesition works for content so hopefully it will work well... But the amount of change means I want to test it a lot before updating the main package to it
Thank you for clarifying.
Hello kevin, Does uSync support now Document Type Deletions Sync?
Thanks /Bilal
Hi
yes, uSync (v3+) fully supports deletions of all the things !
when you delete stuff, it gets logged in the uSyncActions.config file (in side the usync/data folder).
then at the other end this file is used to delete the things.
Kevin
Do I have to delete myself any files from the uSync folder? The other day, this scenario happened with me, where I had to delete a Document Type. Then after that, I noticed an exclamation mark in VS uSync folder for the file I deleted.
When I pushed changes to web, I got my deployment broken and had to delete everything and do a fresh new installation.
Also, I am not sure if you could help me out on this. I had established a web app on Azure together with a staging deployment slot.
I usually publish to staging, then I publish again to production (I don't make use of SWAP). However, for some reason, both were pointing to the same DB, despite the fact I changed the staging to point to staging DB. I solved this by making the staging use SQL Compact and the production use normal SQL. That sounds weird!
So back to the main topic, do I need to make any special configuration to make deletions work?
Thanks /Bilal
is working on a reply...