-
Notifications
You must be signed in to change notification settings - Fork 642
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
[3.7.40.1]: Custom element query #11105
Comments
Which full class name is |
@brandonkelly, It's referencing Befor the update, this was the query that was beeing run:
But after the update, this is the query now:
And here the issue is that it adds |
Gotcha. Got this fixed for the next release. That’s not an intended use of |
Thank you, will note that down - is there a better way to query for multiple elements, and at the same time beeing able to limit them to relations to categories ? Because it's actually tricky to make a commerce category page if you have multiple purchasables in the shop. |
Querying for multiple elements isn’t supported yet. Aware it’s needed, so we’re hoping to come up with a reliable way to do it for Craft 5. |
Craft 3.7.41 is out now with that change, by the way. |
What happened?
These lines prevents custom element query:
cms/src/elements/db/ElementQuery.php
Lines 1353 to 1355 in e9914a9
For instance, in commerce i need to query two elements, to get their ID's for a paginated category page:
Up into the _joinedElementTable was introduced, this was a possible query, where i could get multiple purchasables that was related to a category, but its no possible anymore because the _joinedElementTable now adds element.type to the query, limiting it to base element class.
The text was updated successfully, but these errors were encountered: