{"action":"created","issue":{"url":"https://api.github.com/repos/dotCMS/core/issues/8125","labels_url":"https://api.github.com/repos/dotCMS/core/issues/8125/labels{/name}","comments_url":"https://api.github.com/repos/dotCMS/core/issues/8125/comments","events_url":"https://api.github.com/repos/dotCMS/core/issues/8125/events","html_url":"https://github.com/dotCMS/core/issues/8125","id":105238872,"number":8125,"title":"Push publishing overwrites the site aliases in target site","user":{"login":"aotearoan","id":5041989,"avatar_url":"https://avatars.githubusercontent.com/u/5041989?v=3","gravatar_id":"","url":"https://api.github.com/users/aotearoan","html_url":"https://github.com/aotearoan","followers_url":"https://api.github.com/users/aotearoan/followers","following_url":"https://api.github.com/users/aotearoan/following{/other_user}","gists_url":"https://api.github.com/users/aotearoan/gists{/gist_id}","starred_url":"https://api.github.com/users/aotearoan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aotearoan/subscriptions","organizations_url":"https://api.github.com/users/aotearoan/orgs","repos_url":"https://api.github.com/users/aotearoan/repos","events_url":"https://api.github.com/users/aotearoan/events{/privacy}","received_events_url":"https://api.github.com/users/aotearoan/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-09-07T15:47:02Z","updated_at":"2016-01-27T12:45:27Z","closed_at":"2015-09-08T13:10:38Z","body":"Hi, we have an issue with push publishing overwriting the aliases of the target site sometimes when we change and push even a single item of content. We have a 3 site setup\r\n - publishing pushes to staging\r\n - staging pushes to prod\r\n\r\nHere's what happened:\r\n1. I made a change in a single vtl file and uploaded this to publishing via webdav\r\n2. I push published the single vtl file to staging\r\n3. I push published this change from staging to prod\r\n4. the alias in prod was changed to common-website-publishing.fpprod.corp (the publishing site alias)\r\n5. grepping for \"website-publishing\" in the bundle turned up these results:\r\n\r\n./ROOT/application/570a26d6-408d-4405-a492-b35f353ad87f.folder.xml:        <string>common-website-publishing.fpprod.corp</string>                  \r\n./ROOT/application/themes/ltq-global/4026c75e-e19f-4022-87de-7bac6b7bb3e5.folder.xml:        <string>common-website-publishing.fpprod.corp</string>\r\n./ROOT/application/themes/9024985c-3d87-423c-b07e-ff9a7751c1af.folder.xml:        <string>common-website-publishing.fpprod.corp</string>           \r\n./ROOT/2e9bc260-3399-4930-856a-19e9f40b6542.folder.xml:        <string>common-website-publishing.fpprod.corp</string>                              \r\nROOT/application/570a26d6-408d-4405-a492-b35f353ad87f.folder.xml:        <string>common-website-publishing.fpprod.corp</string>                    \r\nROOT/application/themes/ltq-global/4026c75e-e19f-4022-87de-7bac6b7bb3e5.folder.xml:        <string>common-website-publishing.fpprod.corp</string>  \r\nROOT/application/themes/9024985c-3d87-423c-b07e-ff9a7751c1af.folder.xml:        <string>common-website-publishing.fpprod.corp</string>             \r\nROOT/2e9bc260-3399-4930-856a-19e9f40b6542.folder.xml:        <string>common-website-publishing.fpprod.corp</string>                                \r\n\r\n5. I fixed the alias manually in both staging and prod\r\n6. I made another change to the same vtl file and uploaded to publishing via webdav\r\n7. I pushed this change to staging and then prod\r\n8. This time the alias was unchanged\r\n9. grepping for \"website-publishing\" in the bundle there were no results.\r\n\r\nSo it seems we have this issue when there is a ROOT folder in the bundle with details of the host including the aliases.\r\n\r\nI would expect push publishing not to propagate the aliases at all. I would also expect the push publishing to be deterministic which is clearly is not.\r\n\r\nThis is a very critical bug in push publish and we cannot go live until it is fixed without the risk of our production site breaking any time we push content.\r\n\r\nWe are using dotCMS 3.2.1.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/dotCMS/core/issues/comments/175601212","html_url":"https://github.com/dotCMS/core/issues/8125#issuecomment-175601212","issue_url":"https://api.github.com/repos/dotCMS/core/issues/8125","id":175601212,"user":{"login":"levosgien","id":1823543,"avatar_url":"https://avatars.githubusercontent.com/u/1823543?v=3","gravatar_id":"","url":"https://api.github.com/users/levosgien","html_url":"https://github.com/levosgien","followers_url":"https://api.github.com/users/levosgien/followers","following_url":"https://api.github.com/users/levosgien/following{/other_user}","gists_url":"https://api.github.com/users/levosgien/gists{/gist_id}","starred_url":"https://api.github.com/users/levosgien/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/levosgien/subscriptions","organizations_url":"https://api.github.com/users/levosgien/orgs","repos_url":"https://api.github.com/users/levosgien/repos","events_url":"https://api.github.com/users/levosgien/events{/privacy}","received_events_url":"https://api.github.com/users/levosgien/received_events","type":"User","site_admin":false},"created_at":"2016-01-27T12:45:27Z","updated_at":"2016-01-27T12:45:27Z","body":"The expected behavior here is that the host be updated (alias, name, and other properties) as the rest of your data, meaning not directly in prod but from the sender. Therefor any alias change would be made on your sender(s), and pushed along with any VTLs that need to move over and which reside on that host (saved on it).\r\n\r\nIn the behavior above if I understand correctly the host alias was changed at the prod level directly, which resulted in mismatches and \"data integrity\" discrepancies between that same host in prod/staging. This is your issue right there if that is the case.\r\n\r\nRemember, in push publishing you want one unique source for your data as to avoid data integrity issues.\r\n\r\nFeel free to submit a support ticket for further clarification on the recommended process as changing aliases and updating VTLs multiple times is something that works consistently.\r\n\r\nThank you."}}