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

V14: Don't add published culture infos if not published #15370

Merged

Conversation

Zeegaan
Copy link
Member

@Zeegaan Zeegaan commented Dec 6, 2023

Notes

Problem right now is that when we Unpublish a single culture, that re-published the content, but just without the "unpublished" culture.

When we unpublish all cultures, it works a bit different though. We don't unpublish the cultures. We just unpublished the content itself, and thus the cultures are not routable.
Problem is though the content.PublishedInfos still containted the "Published" cultures.

This PR remedies that by now publishing all cultures instead.

How to test

  • Have some languages on your site
  • Make a document type and allow as root & allow vary by culture
  • Add a Title property to the document
  • Make some content in the different languages
  • Ensure you can publish & unpublish a single culture
  • Ensure you can publish & unpublish ALL cultures
  • Ensure rollback works.

Zeegaan and others added 4 commits January 25, 2024 14:16
…still-persists

# Conflicts:
#	tests/Umbraco.Tests.Integration/Umbraco.Infrastructure/Services/ContentPublishingServiceTests.Publish.cs
Copy link
Member

@bergmania bergmania left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it works as we expect now 👍

@bergmania bergmania merged commit 74db02c into v14/dev Feb 1, 2024
14 of 15 checks passed
@bergmania bergmania deleted the v14/bugfix/content-unpublishing-cultures-still-persists branch February 1, 2024 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants