I have documents where some properties are allowed to vary by culture, and some or not.
When there are content changes made in 1 of the cultures and I want to only publish that culture to another environment the changes are not found for properties that are not allowed to vary by culture. It will show the message "No Changes detected".
When I selected the option 'include unpublished', the changes will be found and I can push them to the target.
Is this expected behaviour or did I make a mistake somewhere?
I would have a check of your version, there where fixes for how individual variant publishing detected and made changed in later versions of uSync.Complte
I'm getting this happen but only between two particular servers.
Latest Umbraco v10, latest Usync v10.
I have a setup with the same code base and 7 regions.
Each has a Live and Stage. Only the "UK" region returns this error. It actually pushes most change but media (images and video) seems to fail to be pushed, I get broken images and failed images and the message at the end shows there are no changes.
I had a few theories / suspicions:
1) The DB has a doc type that has culture variants enabled but there is only a single (matching) language on the site. This has happened as I was testing languages in the initial dev.
2) We have Cloudflare on the live sites. I wonder if there's some issue in the routing of the domain..?
Here's what I've tried so far.
Local -> Stage - works
Local -> Live - works
UAT -> Live - works
Creating a new server profile - fails
Stage -> UAT - works
Downloading stage db - "Stage local" - Live
So it's something particular to the Stage -> Live push. Seems bizarre.
The next thing I'm going to try is cloning live and trying Stage -> New Live
If that works I have to assume it's something "stuck" environmentally... something in an index or cache that's specific between Stage -> Live.
@Kevin - does any of the above provide a hint why this could happen between two specific servers and I can't recreate?!?!
I've cloned the DB for "live" and tried pushing from Stage -> LiveTest and it works.
So there's either something about the particular web app for Live, the routing via Cloudflare or... something "stuck" in cache / indexes between those two environments.
Are there any usync temp files / db entries that I can clear down and try.
Really confused why this would be happening and how to resolve.
The cultures thing rings a bell - When there is only one culture inside an umbraco multi-variant, i seem to remember odd things happen in terms of what the Umbraco API does and doesn't say is published (from memory it says the whole page is published but doesn't say individual culture is - when it is)
I think its something we fixed - i will have to check exactly what version. (if you are on latest its likey not this unless we fixed it for v12, and it hasn't been rolled back into v10 yet 🤔)
the clone then work however is odd.
uSync isn't really caching anything (if you have turned on caching which is off by default in v10 - we cache dependencies, but that is not changes).
I would see if you can avoid cloud flare for the usync commands (esp. going to /umbraco/uSync/usyncreceive)
also what happens if you create a new page and try to push that, does it get picked up as a change (if it doesn't then its almost certainly caching, etc)
Unrelated possibly but just fixed a lot of issues with my Umbraco instance - in particular Content Service.
The site, whilst in dev had - for a while - multiple languages. A doc type had a setting to allow multiple variants (cultures). The languages were later reduced to one but I think this setting was stuck.
This has also caused issues with the Content Service not working (looks fine, doesn't throw an error but then the nodes won't load in the back office with "Cannot save a non-current version").
The fix was I fixed the document type (I used usync but assuming you could add a dummy language, modify in the backoffice then remove the second language). uSync was handy as I could search the text files for this:
FROM:
<Variations>Culture</Variations>
TO:
<Variations>Nothing</Variations>
This might sort my woes with the push publish - will update on Monday - not changing prod on Friday afternoon.
Sometimes it is the most ridiculous mistakes that cause the most frustration and waste the most time as a developer. Here follows my confession:
My issue was the deployment scrips had the wrong variables assigned for the Staging site.
The Live and Stage webapps were both pointing at the same, Live, DB.
So no wonder uSync was reporting an error that there were no changes to make - there weren't. Explains why my media was looking broken (as they did have separate Blob containers).
No changes detected when trying to publish to..
I have documents where some properties are allowed to vary by culture, and some or not.
When there are content changes made in 1 of the cultures and I want to only publish that culture to another environment the changes are not found for properties that are not allowed to vary by culture. It will show the message "No Changes detected".
When I selected the option 'include unpublished', the changes will be found and I can push them to the target.
Is this expected behaviour or did I make a mistake somewhere?
Versions:
@jelger-ribbers did you find a solution to this as I am seeing exactly the same issue in our setup?
Hi Ian,
I have not a 100% solution but I work around it by also selecting the other (unpublished variants).
Hope that helps a bit.
Hi,
I would have a check of your version, there where fixes for how individual variant publishing detected and made changed in later versions of uSync.Complte
I'm using the 12.1 version and is happening too
I'm getting this happen but only between two particular servers. Latest Umbraco v10, latest Usync v10.
I have a setup with the same code base and 7 regions.
Each has a Live and Stage. Only the "UK" region returns this error. It actually pushes most change but media (images and video) seems to fail to be pushed, I get broken images and failed images and the message at the end shows there are no changes.
I had a few theories / suspicions: 1) The DB has a doc type that has culture variants enabled but there is only a single (matching) language on the site. This has happened as I was testing languages in the initial dev. 2) We have Cloudflare on the live sites. I wonder if there's some issue in the routing of the domain..?
Here's what I've tried so far.
Local -> Stage - works Local -> Live - works UAT -> Live - works Creating a new server profile - fails Stage -> UAT - works Downloading stage db - "Stage local" - Live
So it's something particular to the Stage -> Live push. Seems bizarre.
The next thing I'm going to try is cloning live and trying Stage -> New Live
If that works I have to assume it's something "stuck" environmentally... something in an index or cache that's specific between Stage -> Live.
@Kevin - does any of the above provide a hint why this could happen between two specific servers and I can't recreate?!?!
I've cloned the DB for "live" and tried pushing from Stage -> LiveTest and it works.
So there's either something about the particular web app for Live, the routing via Cloudflare or... something "stuck" in cache / indexes between those two environments.
Are there any usync temp files / db entries that I can clear down and try.
Really confused why this would be happening and how to resolve.
Hi,
The cultures thing rings a bell - When there is only one culture inside an umbraco multi-variant, i seem to remember odd things happen in terms of what the Umbraco API does and doesn't say is published (from memory it says the whole page is published but doesn't say individual culture is - when it is)
I think its something we fixed - i will have to check exactly what version. (if you are on latest its likey not this unless we fixed it for v12, and it hasn't been rolled back into v10 yet 🤔)
the clone then work however is odd.
uSync isn't really caching anything (if you have turned on caching which is off by default in v10 - we cache dependencies, but that is not changes).
I would see if you can avoid cloud flare for the usync commands (esp. going to /umbraco/uSync/usyncreceive)
also what happens if you create a new page and try to push that, does it get picked up as a change (if it doesn't then its almost certainly caching, etc)
Cloudflare is set so that everything is cached except calls to /Umbraco* (otherwise API calls wouldn't work, and the back office wouldn't work).
I did try disabling all cache and trying to recreate and it still had the same message.
A new page has exactly the same issue. It deploys but shows the "No Changes"
message.
To rule out Cloudflare further i just bound a secondary domain to the live server live.mydomain.com and pushed via that. Same message.
Unrelated possibly but just fixed a lot of issues with my Umbraco instance - in particular Content Service.
The site, whilst in dev had - for a while - multiple languages. A doc type had a setting to allow multiple variants (cultures). The languages were later reduced to one but I think this setting was stuck.
This has also caused issues with the Content Service not working (looks fine, doesn't throw an error but then the nodes won't load in the back office with "Cannot save a non-current version").
The fix was I fixed the document type (I used usync but assuming you could add a dummy language, modify in the backoffice then remove the second language). uSync was handy as I could search the text files for this: FROM:
TO:
This might sort my woes with the push publish - will update on Monday - not changing prod on Friday afternoon.
Sometimes it is the most ridiculous mistakes that cause the most frustration and waste the most time as a developer. Here follows my confession:
My issue was the deployment scrips had the wrong variables assigned for the Staging site.
The Live and Stage webapps were both pointing at the same, Live, DB.
So no wonder uSync was reporting an error that there were no changes to make - there weren't. Explains why my media was looking broken (as they did have separate Blob containers).
Oh no .. i feel your pain, I spent 1/2 a day last week compiling the wrong version of a package, and wondering why i was getting odd errors.
glad it is working now !
is working on a reply...