I don't follow the logic of that Ticket's Summary of the resolution:
"Problem: I would like to display more than 50 results in an unpaginated View."
If a view is not paginated, it will, of course, display all posts, and if you have 56 posts, it would display 56.
If you have 10, then 10.
I also see that code sets the posts per page (so it is indeed a paginated View!) to the extremely huge amount of 67890 (!!) posts per page.
This will probably kill the website as it will underperform in the query. WordPress cannot list that many posts for several users (potential visitors) at once.
Views use just the WordPress query, so we are bound to it.
Clearly, following the threads' origins, this code is made to actually make Views with pagination, not unpaginated as described in the ticket's summary.
I have updated Christian to please adjust that.
The original thread is here:
https://toolset.com/forums/topic/make-more-than-50-posts-show-on-paginated-view/
The correct thing to do here is to add a feature request here https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/, asking to actually allow manual input on the pagination (items per page) settings. Then, you can add manually a number there, be it 1, 100 or 10k, and are not bound to the Selector as it's offered now.
Now, if you want to have this working now since the feature (if you are going to request it) will take a longer time to be implemented, then yes you need that Custom Code.
The Custom codes generally are added to the Theme's functions.php file, or, in Toolset > Settings > Custom Code (last tab) you can add it directly within our plugins - it's a lot safer because we check the code before applying it automatically, so you can avoid fatal errors 😉
Hope I could be of any help with this and that the details above clarify the task!
