You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a collection referes to another collection with an MSO relationship, and the related collection is a singleton, the drawer of the M2O interface doesn't show the singleton item - the drawer is just blank.
Screen.Recording.2023-03-07.at.08.33.01.mov
To Reproduce
Create a collection as and mark it as singleton
Create another collection with a M2O relationship to the singleton collection
Open the collection with the related singleton collection and click on the m2o interface.
The drawer will open but will not contain an item.
When the collection from step 1 is not a singleton, the behavior is as expected so the items will appear in the drawer and one can be selected. But when the collection is a singleton, no item is shown.
Hosting Strategy
Self-Hosted (Custom)
The text was updated successfully, but these errors were encountered:
I'm wondering what the right approach to solve this would be. We could fix the bug to support singletons in relations, but then you could end up with multiple singleton items in the database even though the app can only ever show one, which is not good at all. We could also do as the m2a is currently doing it by disallowing to select singletons on the relation which makes sense to me.
Checklist
Describe the Bug
When a collection referes to another collection with an MSO relationship, and the related collection is a singleton, the drawer of the M2O interface doesn't show the singleton item - the drawer is just blank.
Screen.Recording.2023-03-07.at.08.33.01.mov
To Reproduce
The drawer will open but will not contain an item.
When the collection from step 1 is not a singleton, the behavior is as expected so the items will appear in the drawer and one can be selected. But when the collection is a singleton, no item is shown.
Hosting Strategy
Self-Hosted (Custom)
The text was updated successfully, but these errors were encountered: