-
Notifications
You must be signed in to change notification settings - Fork 29
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.
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
Datasource-grouping only works for first associated section #86
Comments
Hum that's weird. |
Yep. Just replicated the exact same issue with the following Setup:
|
A few screenshots to illustrate my test-setting: Section "Projects"Section "News"Section "Images"Section "Images" - "Parent Entry" Selectbox Link FieldFrontend Test CaseNow I build a datasource "projects" including all 4 entries from the "projects"-section, another datasource named "news" including all 4 entries from the "news"-section and a third datasource named "images" that is filtered by the ds-params of the first two datasources. The filter-settings look like this: If a don't activate grouping the output of the datasource "images" looks like this: If i activate grouping by "parent entry" the output changes to this: So obviously datasource-grouping by entries of a SBL- or association-field doesn't work as expected if the SBL- or association-field contains entries from multiple sections. |
The problem I see are missing records, but the order seems correct (A is before C). I am right ? Also, what happens if you change the order direction (meaning it should find a News entry before a Project entry) Thanks for those super awesomely detailed explanation @twiro |
I have the following scenario:
This results in the following buggy behavior:
As soon as I turn off grouping all expected image-entries (of both parent-sections) are included in the datasource again. I also tried switching to a more fancy name than "entry" for the SBL-field - doesn't do a difference. I also tested this scenario with Association Field - obviously has the same bug.
Setup:
The text was updated successfully, but these errors were encountered: