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.

Sign up for GitHub

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

Jump to bottom

setcontent order does not work if field is not localized but content is #1772

Closed
I-Valchev opened this issue Aug 25, 2020 · 0 comments · Fixed by #1774
Closed

setcontent order does not work if field is not localized but content is #1772

I-Valchev opened this issue Aug 25, 2020 · 0 comments · Fixed by #1774
Labels
🐛 tag: bug This is a bug.
Milestone
Bolt 4.0.0 stable

Comments

@I-Valchev
Copy link
Member

If the contenttype has defined locales and we have a field, e.g. date which is not localized, we cannot order by it (because it returns 0 results).

Bolt should be smart enough to not put the condition that the locale be the same, if the field is not localized.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 tag: bug This is a bug.
Projects
None yet
Milestone
Bolt 4.0.0 stable
Development

Successfully merging a pull request may close this issue.

Fix orderby non-localizable field in localized contenttype bolt/core
1 participant
@I-Valchev