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

Publish with decendants does't reflect on the nodes published in Back Office #17345

Closed
StudioBravo opened this issue Oct 23, 2024 · 3 comments
Closed

Comments

@StudioBravo
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

14.3.1

Bug summary

When the content editors use "Publish with decendants" option to publish a parent node on a node with unpublished child nodes, some of the child nodes still indicates unpublished status but it is actually published (browser referesh indicates the item is published).

Specifics

No response

Steps to reproduce

  • Pick up a parent document with a list of unpublished children

image

  • Select "Publish with decendants" and select "Include unpublished content items"

image

  • Click on Publish with decendants
  • The UI indicates some of the nodes are unpublished but when the browser is refreshed, the correct publish status is shown

image

Expected result / actual result

The UI should reflect the correct status (published) when "Publish with decendants" is applied on the parent.

Copy link

Hi there @StudioBravo!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@Zeegaan Zeegaan self-assigned this Oct 23, 2024
@Zeegaan
Copy link
Member

Zeegaan commented Oct 23, 2024

I can reproduce this, thanks for reporting! 🐛

@leekelleher
Copy link
Member

Fixed in umbraco/Umbraco.CMS.Backoffice#2486 for v15.0.0-rc3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants