Closed andrewconnell closed 8 years ago
This is a result of a list with too many IDs. What does you projection query configuration looks like?
It looks the same as the one I referenced in the issue, linked to the post. I accepted all defaults when creating it. Works fine when I preview the query in the admin, but when viewing the projection page, it fails...
The admin preview queries just the first 10 items, thats why it's working there. Did you perhaps changed Maximum items
to 0?
Nope… I left it at 20
Try setting Items to display
to 10.
Same effect
This is definitely the issue, your filter is somehow not setting a COUNT to limit the number of results, then SQL Server can't handle all the requested items in a single query. I would be surprised to find a bug in this part of the code, it's very well tested and hasn't had any change for a long time. Can you try with a new query? Also, you really want the Create date, not the publish date, I have already insisted on this, PLEASE PLEASE skype me so you understand why this is what you want.
My bad… the default had the number of items set to 0, so it was going unlimited. When I set it to 20, it fixed it.
Now order by Create Date ;)
I created a query for all blog posts sorted in descending order by publish date and rendered using an unordered list, using this post as a guideline: http://weblogs.asp.net/bleroy/easy-custom-rss-in-orchard
I then created a projection for the query, but when I went to view it, I got an error... from the stack, the query is massive... why so big?