The client is pushing up a singular piece of content. We expect:
The content node
The doc type
The template file & related views
However, it appears to be pulling in multiple other views that are not directly related the content piece. I've attached a screenshot which shows views that are not at all related to the content outlined in red. Do you have any idea why this may be happening? The files have been updated (related to another change) but since they are not related to the content node we're attempting to push up, I wouldn't have expected them to be in the package.
unfortunately when we pushing the files between sites, uSync doesn't know which files are needed, so we sync all file changes.
This is because while we can say which template is associated with a document ,we can't for certain say which other files are linked to that template.
For example if the template requires a partial that may be linked via a Html.Partial call, but equally it could be in a surface controller or IAction method within compiled code.
this means we can't reliably parse all the site code to get this dependency change for all the files. So we sync all the changed files to ensure we don't miss anything.
uSync Publisher pulling unrelated dependencies Umbraco 8
The client is pushing up a singular piece of content. We expect:
The content node The doc type The template file & related views
However, it appears to be pulling in multiple other views that are not directly related the content piece. I've attached a screenshot which shows views that are not at all related to the content outlined in red. Do you have any idea why this may be happening? The files have been updated (related to another change) but since they are not related to the content node we're attempting to push up, I wouldn't have expected them to be in the package.
Hi Stephanie,
unfortunately when we pushing the files between sites, uSync doesn't know which files are needed, so we sync all file changes.
This is because while we can say which template is associated with a document ,we can't for certain say which other files are linked to that template.
For example if the template requires a partial that may be linked via a Html.Partial call, but equally it could be in a surface controller or IAction method within compiled code.
this means we can't reliably parse all the site code to get this dependency change for all the files. So we sync all the changed files to ensure we don't miss anything.
we do have an outstanding issue, we are looking at that will allow you to push individual files/folders from the settings section, but we are still working on that, because at the moment all files are synced in a block.
is working on a reply...