- 🇺🇸United States smustgrave
Wonder if you could provide steps you took to produce this bug?
- Status changed to Closed: cannot reproduce
9 months ago 12:45am 2 October 2024
When listing the contexts available the trait uses ContextHandler::getMatchingContexts which validates against the context definition by data type as well as any constraints.
This can prevent contexts which are not always available from being selected on forms. For example, a plugin with a context definition with a NotNull constraint will not match any contexts returned form getAvailableContexts without a value.
It seems to me that when listing available contexts only the data type should be considered and any constraint validation should be left until runtime. This does have an obvious side effect of allowing the selection of contexts that aren't always available and thus may not be available at runtime, resulting in exceptions.
Postponed: needs info
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Wonder if you could provide steps you took to produce this bug?
