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

Publishing with Schedule doesn't work correctly #15340

Closed
kpgphoenix opened this issue Dec 1, 2023 · 3 comments
Closed

Publishing with Schedule doesn't work correctly #15340

kpgphoenix opened this issue Dec 1, 2023 · 3 comments
Labels
state/needs-more-info We don't have enough information to give a good reply state/needs-reproduction Check if this can be reproduced in the latest released version type/bug

Comments

@kpgphoenix
Copy link

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

12.3.3

Bug summary

When node is schedule to be published in the future, it doesn't get published correctly. In the history there is an entry that the node has been published but at the same time in the Publish Menu on the bottom right corner the "Unpublish" option is missing and the node is not available on the content delivery API nor can't it get retrieved by the UmbracoContext.Content.GetById() method when preview is set to false. There is also no ContentPublishedNotification triggered.

image

Specifics

No response

Steps to reproduce

Create and save a node
Create a publish schedule for a future date and time
Try to retrieve the the node via UmbracoContext or Content Delivery API after the schedule date.

Expected result / actual result

No response

Copy link

github-actions bot commented Dec 1, 2023

Hi there @kpgphoenix!

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 🤖 🙂

@kjac
Copy link
Contributor

kjac commented Dec 3, 2023

Hi @kpgphoenix,

Thanks a lot for reaching out 👍

Unfortunately I can't reproduce this. Here's my test on v12.3.3:

Step 1

I've created some variant content. The content is unpublished in all languages. I have set the Danish language version to be published at a specific time:

image

Step 2

After the publish time, the Danish language variant is published, and the unpublish option appears:

image

Step 3

Querying the specific item for the Danish culture in the Delivery API yields the Danish language variant:

image

Step 4

Querying all items for the Danish culture in the Delivery API yields the single published item in its Danish language variant:

image

If the issue still persists with you, could you please supply additional steps to reproduce?

Could this issue be tied to custom code executing in your site?

@kjac kjac added state/needs-more-info We don't have enough information to give a good reply state/needs-reproduction Check if this can be reproduced in the latest released version labels Dec 3, 2023
@elit0451
Copy link
Contributor

Since we cannot reproduce the issue and we haven't heard from you, @kpgphoenix, in a while, I will go ahead and close it. Feel free to reopen it if you can share some more details 🙂

Have a joyful new year! 🎊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/needs-more-info We don't have enough information to give a good reply state/needs-reproduction Check if this can be reproduced in the latest released version type/bug
Projects
None yet
Development

No branches or pull requests

3 participants