https://discord.umbraco.com logo
Join Discord
Powered by
usync unpublish - push node that's been unpublishe...
# help-with-umbraco
s
For a page that's been pushed from the staging site to live - how would an editor then unpublish this node? I thought I could push after unpublishing but it doesn't seem to do anything.
y
Hello @SiempreSteve , Did you try to unpublish it from the node it self? or from the backoffice page it self ?
k
Hi Steve, what version of Umbraco/uSync do you have - because i just tried that on the latest version and it worked 😦
s
10.5.0 on Umbraco v10 latest.
I shall update this, release and retry when I get a chance.
Just did. Same on latest usync?! I'm pushing the unpublished node rather than the parent.
k
Humm, i'll have to take a deeper look, because just tried it on v10 and it works for me there too. (so i am unpublishing a node ,then right click push that node to the other server, where it becomes unpublished) ?
s
Yes - that's what I'm doing!?
Might be a red herring but
I do see this in the log?
k
Ahhh - languages , I wasn't triing with languages set - thats a totally diffrent thing unpublishing languages... let me take a look
how many languages does your site have installed (in settings / languages) and how many language versions are their of this page ?
i think if you have your content set to 'vary by content' but then their is only one language on the site, uSync tried to perform the generic 'unpublish' (where in unpublishes the page) when it should in fact perform the language unpublish (where it unpublishes the language). It all works if you have multiple languages or a single languge site that doens't vary by culture 😞 - so looks like its something we will have to take a look at.
s
I did have multiple languages - there's only en-gb now
It's actually something I might struggle with. One code base - we deploy to multiple servers. Run usync for new pages / blocks. But don't want to push over the language on that regional site
I hoped (thought) I could just ensure the usync languages folder is always empty (or configure it not to output this)
k
yeah when there are multiple languages uSync can only write certain languages to the targets, but it sort of assumes you are starting with more than one language, its in the logic of how it knows if the site is multi-lingual or not, and if the user has decided to sync all languages or not. (when you select all languages, things like shared 'non' vary by culture elements are also synced, when you sync by 'some' languages those values don't come across.
Its something that can probibly be worked out - but your main problem pushing from a site with one language to a site with multiple languages is what happens to any content that is shared between languages (e.g anything that doesn't have vary by culture)
because when you send from a single site, uSync things you have all the languages selected (because you do) so it will also sync non-shared content
s
Here though this is a stage (en-gb) -> live (en-gb) only
(double checking...)
Yes - that's right. I think when I started devving the site I played around with the translations on the page doc type. I wonder if it's stuck in there taht some propreters are culture specific...
k
We might be chasing an Umbraco bug (but i am checking) - when you unpublish a single page languge. Umbraco sets Item.Published to false but it doesn't also set the culture to published to false, so item.IsCulturePublished(culture) returns true. so actually looking at what is happening that is where we are falling down inside uSync.
Now that we know this , we can work around it .
nightly release https://dev.azure.com/jumoo/Public/_artifacts/feed/nightly/NuGet/uSync/overview/10.7.2-build.20231109.2 with this one fix in it ( https://github.com/KevinJump/uSync/commit/4945a0e45de74231e400ccf1fd834d2fd258097f ) will fix this issue - I need to confirm it doesn't break something else / another type of setup before we push it as a general release (also need to check if v12 does the same 😦 )
s
@Kevin Jump - apologies - I completely missed your replies to this. Site has now gone live and we thought usync was working even though it was doing it's business then showing a message saying nothing had changed. I think it's this bug. I'll clone the db - spin up a test environment and see if this nightly has the same issue. What I'd really like to do is fix my Umbraco db though. You hint you think it might be because some doc types have culture specific properties - any suggestions for how to resolve this (my thought is actually to inspect the usync doc type export and see if I can fix via your xml?
I tried to install the nightly (by running Install-Package uSync -version 10.7.2-build.20231109.2) and i get errors about dependences on v11 umbraco?
message
k
i think that missing the package feed ? (https://dev.azure.com/jumoo/Public/_artifacts/feed/nightly/connect) so the install is looking for the nightly build, but when it can't find it its going for the next best thing which is 11.0.0-rc3 (which is published on nuget).
I am not sure there is much reason why we can't publish 10.7.2 now other than just needing a little time to do the release checks. etc
s
Just tried adding that url as a package source then rerunning the install package command - now get: Install-Package : NU1301: Failed to retrieve information about 'uSync' from remote source 'https://dev.azure.com/jumoo/Public/_artifacts/feed/nightly/connect/FindPackagesById()?id='uSync'&semVerLevel=2.0.0'. At line:1 char:1
2 Views
PreviousNext
Powered by