Re: bug in DB_Pager
| From: | Demian Turner | Date: | Sun, 08 Jun 2003 09:51:33 +0000 |
| Subject: | Re: bug in DB_Pager | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17167@lists.php.net to get a copy of this message | ||
Richard
I hadn't seen your mod, thanks for pointing this out :-) I've used DB_Pager in about 50 scripts and was about to embark on the somewhat painful conversion to Pager because my customers don't can't seem to appreciate the 'googleness' of DB_Pager's default output.
When Alain pointed out that DB_Pager actually follows Google's example I was surprised as I hadn't noticed after so many Google searches the incrementing maxpages.
To the maintainers, can Richard's mod be considered as an alternative output for the official DB_Pager, either in its own method or referenced with an optional DB_PAGER_FIXED_MAX_PAGES argument?
cheers
Demian
Richard Wall wrote:
On 2003-06-03 21:44, Demian Turner wrote:I see what you mean, I hadn't noticed beforehand that Google does this as well. Seems quirky, I'd be curious to know how to disable the 'feature' and get just 10 links throughout the resultset.I know what you mean. I submitted an alternative a while ago, but am not sure that it ever got added... http://marc.theaimsgroup.com/?t=102742059100001&r=1&w=2 -RichardWall.