We and a lot of other merchants rely on the need to get way more then 250 items to display data in custom pages. This is absolutely not working with “next” page user interaction. In our case we show a page with all the brands. Now it just cut’s off and there is no good way to get around this part.
We and a lot more merchants would really need this to be in the list here: Liquid tags
Hi @AdminGh — can you share a bit more about your use case? Querying every metaobject in a shop is an expensive, unbounded operation and there are usually better ways to fetch the relevant data, such as a metaobject reference list metafield on the corresponding resource.
Now it just stops and there is no way around this in liquid. If a merchant uses this as a stand alone entity (and a lot do because of the beauty of the Metaobject ifself) then the get this from the corresponding resource is totally not in the use case of a lot of merchants. This is a significant drawback and really limit the use cases of this fantastic concept.
You can try something like this, it works on my end up to 1000 entries:
{% liquid
assign entry_count = metaobjects.type.values_count
assign entry_list = metaobjects.type.values
paginate entry_list by entry_count
for entry in entry_list
# Here, you have access to the individual metaobject entries
# Always paginated to the correct number, up to 1000 entries
endfor
endpaginate
%}