The current logic uses the interface language.
This is a problem for multilingual sites where the user has set their interface language to e.g. english, but manages content in several languages.
The attached MR should resolve this issue.
nick dewitte → changed the visibility of the branch 3283090-browser-should-only to active.
nick dewitte → changed the visibility of the branch 3283090-browser-should-only to hidden.
nick dewitte → made their first commit to this issue’s fork.
We were having some issues with this.
In our case, the latest revision wasn't always used with the canges from MR69, resulting in stale (or missing) scheduler data.
The attached patch aims to resolve this by explicitly loading the latest revision.
The translations of the entity are also being iterated, to take into account scheduling settings on non-default entity translations.
I'm unsure this is the way to go, so I've attached this as a separate patch.
Seems like this was fixed in commit be510aa5a3adaffe462417cdc61975fdb4c299c8, which was included in v4.0.1
nick dewitte → created an issue.
We've had some issues applying #45, so here's a reroll.
Created a patch that replaces the domain based on https://github.com/Choices-js/Choices/commit/0dae0283740f4f619c7589e7b16...
For future reference, this behavior can be (conditionally) bypassed by implementing the following hook:
hook_jsonapi_entity_filter_access()