-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Trying to search within a content type seems to be broken in 3.1.0. #7138
Comments
Hi, I cannot reproduce this. Is this a new project ? |
Hmm. No I started on 3.0.5 and then followed the migration guide to 3.1.0.
During the database migration there were problems. Increased the max pool
and it worked. Could it be that the db migration hasn't worked properly?
…On Thu, 23 Jul 2020, 15:45 Alexandre BODIN, ***@***.***> wrote:
Hi, I cannot reproduce this. Is this a new project ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7138 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJP3IUZEXDRVARW3JWN4WLR5A5IFANCNFSM4PFWTWRQ>
.
|
Do you have any logs of the errors you got ? |
No, but it was this: This is the error when seraching
It happens with all the content types not just users. If I drop and create the db so that it's empty, then rebuild the admin ui it still happens. |
can you share your user model settings.json ? |
|
It also fails after creating a new content type with just one field: "name"
|
Ok I've narrowed it down. It happens when you sort and query at the same time.
It only happens when the sort is added, otherwise it's fine |
Hi, I'll dig into it. Thank you :) |
Thanks! |
I couldn't reproduce the issue. Do you have any more info ? Some custom code that could be related (extensions). |
I'll try. But if I can't without the full project (which seems likely) any hints as to where to look for the issue? |
Here's my deps "dependencies": { |
Same problem here. Happens on all content types.
|
The error can be reproduced:
|
You should check the extensions you made to the user permissions plugin for sure ! it was modified to allow for admin features. |
Thank you, I reproduced it with postgresql. We will dig into it! |
Hey, sorry it seems like you've only fixed the count search. Normal search with filters also fails: |
It works on my side. How did you try it? Did you checkout on branch master? (as version 3.1.2 is not published yet) |
Describe the bug
Trying to search within a content type seems to be broken in 3.1.0. It fails with a 500 error.
This is the error:
error: column "users-permissions_user.username" must appear in the GROUP BY clause or be used in an aggregate function
Steps to reproduce the behavior
Expected behavior
That searching works.
The text was updated successfully, but these errors were encountered: