Skip to content

Conversation

@AaronClaes
Copy link
Contributor

What?

When you have multiple locales and required localized fields, the orderable functionality breaks.
This happens when you create documents in a locale that is not the default and try to reorder.

The reorder operation uses the default locale, which will have empty data in this case, and fails because the required fields are not filled in.

For more info, see #14684

Why?

Currently it is impossible to reorder items when the active locale has valid data, but the default locale does not.

How?

By passing the active locale to the endpoint, the validation will run against for the active locale, instead of the default locale.
Which allows the operation to succeed.

Before:

${config.serverURL}${config.routes.api}/reorder

After:

${config.serverURL}${config.routes.api}/reorder?locale=${localeCode}

Fixes #14684

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.

Orderable operation validates against default locale instead of active locale

1 participant