RyanJ Posted August 25, 2013 Share Posted August 25, 2013 I am currently using pagination on my search results and just realized that I get a 404 error for any page number exceeding 999. works fine www.mysite.com/url/search/page999/ Does not work, 1000 or greater returns 404 www.mysite.com/url/search/page1000/ Link to comment Share on other sites More sharing options...
owzim Posted August 25, 2013 Share Posted August 25, 2013 That might be a bug/unwanted behavior in core, don't know. But honestly: 999 pages in a pagination? Sounds highly user-unfriendly. I hope your'e just filing a bug here and don't really use so many pages in a pagination =) 1 Link to comment Share on other sites More sharing options...
Martijn Geerts Posted August 25, 2013 Share Posted August 25, 2013 Have you enabled template caching ? Something tells me it works till 999.. Make it stop at 999 then. Most likely people are not interested in the 999 page or 100. I think it's better if result are that high to tell the user to narrow the search. (Youtube api is doing the same, stops at 999) Link to comment Share on other sites More sharing options...
RyanJ Posted August 25, 2013 Author Share Posted August 25, 2013 It's very unlikely such a search would be performed, but i caught it during some testing, so i guess it would be possible. Cache is not enabled and if i understand correctly GET variables are not cached anyway? Requiring the user to limit the search is a great idea though. 1 Link to comment Share on other sites More sharing options...
teppo Posted August 25, 2013 Share Posted August 25, 2013 This is intentional behavior. Personally I'd prefer to have this as a config setting somewhere, though, just to cover those (admittedly very rare) cases where huge pager makes sense. 6 Link to comment Share on other sites More sharing options...
ryan Posted August 29, 2013 Share Posted August 29, 2013 It's important for there to be a hard limit on page numbers just from a caching perspective. You don't want to have anything in your site that can generate an unlimited number of cache files and fill up the hard drive. But that doesn't mean the limit has to be 999, just that 999 is what I perceived to be the upper limit of what would ever be even remotely practical to support in pagination. I'm fine with making this configurable though, but hope you guys use it to configure the number down rather than up. 3 Link to comment Share on other sites More sharing options...
diogo Posted August 29, 2013 Share Posted August 29, 2013 I'm fine with making this configurable though, but hope you guys use it to configure the number down rather than up. Or even better. By making it configurable, you can perfectly have a much lower default. 1 Link to comment Share on other sites More sharing options...
RyanJ Posted May 3, 2014 Author Share Posted May 3, 2014 Hey Ryan, hope all is well. Was the option to make the page number configurable ever added? Link to comment Share on other sites More sharing options...
Soma Posted July 4, 2014 Share Posted July 4, 2014 Yes here $config->maxPageNum = 999; It's set in wire/config.php but you would add it to your site/config.php 2 Link to comment Share on other sites More sharing options...
RyanJ Posted July 5, 2014 Author Share Posted July 5, 2014 Thank you Soma, I appreciate it. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now