I made a change in the backoffice (added a property to a doc type) and it updated my uSync file. Then I manually edited the file, but when I ran the report, it didn't pick up the change. Is this by design?
for content - the update is done based on the update date property. if that property is older (or the same) in the file as to that on the disk the update doesn't happen. change the update date attribute in the file to something in the future.
for all but content: (assuming we are talking v3), then your change should be picked up.
for an import uSync actually creates an export file in memory and then compares that to the one on disk, if they are different an import will happen.
(older v2 usync files) - in v2 usync has a hash value in the xml file - if this is compared to the internal versions hash - to make a manual change you need to change the value of this hash value (you can just put anything in it).
The november uSync update (i.e the thing i haven't finished yet) is going to include the option to have content behave the same way as the rest of usync. (so file mismatch = update) I've just held of on this as a default because you might not want your old content wiping newer stuff.
I think I may have asked you this before regarding content, but if I don't want uSync to update blog posts and faqs, it won't do it if the update date of the blog posts on file is older than what is currently on umbraco, correct?
Also, since it writes it to disk, I could exclude those content types from source control, is that correct?
As far as your November update, I would not want older stuff wiping newer stuff.
If I manually change a uSync file, why isn't it picked up?
I made a change in the backoffice (added a property to a doc type) and it updated my uSync file. Then I manually edited the file, but when I ran the report, it didn't pick up the change. Is this by design?
Hi
it depends a bit on the file.
for content - the update is done based on the update date property. if that property is older (or the same) in the file as to that on the disk the update doesn't happen. change the update date attribute in the file to something in the future.
for all but content: (assuming we are talking v3), then your change should be picked up.
for an import uSync actually creates an export file in memory and then compares that to the one on disk, if they are different an import will happen.
(older v2 usync files) - in v2 usync has a hash value in the xml file - if this is compared to the internal versions hash - to make a manual change you need to change the value of this hash value (you can just put anything in it).
The november uSync update (i.e the thing i haven't finished yet) is going to include the option to have content behave the same way as the rest of usync. (so file mismatch = update) I've just held of on this as a default because you might not want your old content wiping newer stuff.
Thanks Kevin,
I think I may have asked you this before regarding content, but if I don't want uSync to update blog posts and faqs, it won't do it if the update date of the blog posts on file is older than what is currently on umbraco, correct?
Also, since it writes it to disk, I could exclude those content types from source control, is that correct?
As far as your November update, I would not want older stuff wiping newer stuff.
Thanks Saied
is working on a reply...