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

GraphQL: get content items with "satus: ALL" returns only published items #17115

Closed
AndreySurkov opened this issue Dec 4, 2024 · 1 comment · Fixed by #17116
Closed

GraphQL: get content items with "satus: ALL" returns only published items #17115

AndreySurkov opened this issue Dec 4, 2024 · 1 comment · Fixed by #17116
Labels
Milestone

Comments

@AndreySurkov
Copy link
Contributor

Describe the bug

In GraphQL when I request items with status ALL it should return all version of items (including deleted). It works in this way in OrchardCore 1.8.2

page(status: ALL) {
    displayText
}

But in OrchardCore 2.1.0 it returns only published versions of items.

Orchard Core version

2.1.0

Logs and screenshots

This change was intoduced in https://github.com/OrchardCMS/OrchardCore/pull/16077/files

image

@AndreySurkov AndreySurkov changed the title GraphQL: get content items with satus=All do not returnt all versions GraphQL: get content items with "satus: ALL" returns only published items Dec 4, 2024
MikeAlhayek added a commit that referenced this issue Dec 4, 2024
@MikeAlhayek MikeAlhayek added this to the 2.x milestone Dec 4, 2024
Copy link
Contributor

github-actions bot commented Dec 4, 2024

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

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

Successfully merging a pull request may close this issue.

2 participants