Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unpublish not unpublishing on target #125

Closed
IRooc opened this issue Jul 27, 2021 · 7 comments
Closed

Unpublish not unpublishing on target #125

IRooc opened this issue Jul 27, 2021 · 7 comments
Assignees
Labels
bug Something isn't working release/8.10.3 Patch release

Comments

@IRooc
Copy link

IRooc commented Jul 27, 2021

Describe the bug
We have two servers, staging and production. Publishing items on staging and publish to server production works fine. But when we unpublish on staging and call "publish to production". The dialog mentions that the Published boolean will be set to false (for the default culture) but on the target (production) the changelog is "Save" and "Publish" instead of unpublish.

Staging log:
image

Production log:
image

Version (please complete the following information):

  • Umbraco Version: 8.15
  • uSync Version: v8.9.3 + Content Edition (v8.9.3), Snapshots (v8.10.1), Exporter (v8.10.1), PeopleEdition (v8.10.1), Publisher (v8.10.1), Complete (v8.10.1)

To Reproduce
Steps to reproduce the behavior:
We have a 'vary by culture' doctype setup but currently only with 1 default culture en-GB

  1. Go to staging server create content for default language
  2. Click on publish to to deploy this change to production
  3. On staging click 'unpublish' to unpublish the item
  4. On staging click on publish to to deploy this change to production
  5. On production the item is still published

Expected behavior
The item is also unpublished on production

Screenshots
Change log on staging before publish
image

Report on staging after publish
image

@KevinJump KevinJump self-assigned this Jul 27, 2021
@KevinJump
Copy link
Member

Looking into this now.

@KevinJump KevinJump added the bug Something isn't working label Jul 27, 2021
@IRooc
Copy link
Author

IRooc commented Jul 27, 2021

Just did a PULL from staging to our local dev environment and it pulled the draft but published the item as well.

@KevinJump
Copy link
Member

Looks like its a Umbraco version thing :( - works on our base install (which is quite old v8.1) - on fresh v8.15 we do see thls issue)

having a look to see if we can find out why.

@patrickdemooij9
Copy link

I wonder if it might be related to this issue: umbraco/Umbraco-CMS#10695

@KevinJump
Copy link
Member

yes - Looks something like that :(

line : 106 of the content serializer

           published.Add(new XElement("Published", item.IsCulturePublished(culture),
                    new XAttribute("Culture", culture)));

is returning true and false on the same site depending on how its called 😕

image

Will see if i can identify why - and report into issue if its the same thing

@KevinJump
Copy link
Member

KevinJump commented Jul 27, 2021

I think its not the same issue, but it is debatably a umbraco bug.

if you have a variant with a single culture and you unpublish the single culture. then the publishedCultures value of the content item still contains the culture although the overall item.published value = false.

I am guessing when you completly unpublish an item by unpublishing all its languages - that doesn't wipe the publishedCultures value but it does set the master unpublished value.

we can work around this in uSync. and if i can work out where this happens in Umbraco.Core i will log an issue on the main repo. because i think this is confusing.

@KevinJump
Copy link
Member

Workaround for this issue, in uSync - will be part of next uSync release.

@KevinJump KevinJump added the release/8.10.3 Patch release label Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release/8.10.3 Patch release
Projects
None yet
Development

No branches or pull requests

3 participants