If you are having problems with ajaxPager please report bugs or request support on the jQuery ajaxPager project page. Please make sure you include details on replicating the problem, including browser details, with a url to either an example or example code in paste bin or equivalent service.

People have been posting bugs on the comments and I’ve completely lost track of them. This is partly my fault as I should have correctly earlier, but if people could move there bugs over to the project page it should make it easier for me to manage them.

Thanks

I’ve been so busy both at the University of Kent and with my freelance projects that unfortunately this site and my open source project ajaxPager have gone a little neglected. This evening I stole some time to add some of the projects I’ve been working.

Be sure to check them out in the portfolio

Hopefully I’ll be able to find a bit more time to spend some time fixing the problems people have been finding with the ajaxPager. Having said that I quite bit of stuff lined up so can’t promise anything.

Firstly an apology to the piss poor performance of my site recently, it was never great but recently its gone from bad to worse. Having done a little Googling around and testing I can only put this done to Media Temple’s Grid Server. I’ve just finished a year subscription so will be looking for some new hosting very soon.

Which leads me secondly to apologise for the lack of post, which in part has been due to this performance issue and in part but I have been soooo busy.

Fixed a “pager.linksE is undefined” error, hopefully the same one people are reporting in the comments.

Just a quick patch with a typo fix in it.

After quite a bit of tinkering and documenting (was really tired for this, if you need extra help please contact me) 0.4 is ready. There are quite a few new features, check out the change log for more details, but of significance is:

Support for IE 6 through 7 (in addition to Safari 4 and FF 3, I expect chrome works fine too)
Animations
Methods to add and remove pages

Not many features left to implement for 1.0, the bulk of the work left to do is to bring it in line with jQuery UI practices included support jQuery supported browsers.

0.5 might be a little way off as I’m going to be spending some more time on the project that the ajaxPager was started for but if anyone submits any bugs I will try and fix these in a patch quickly.

Just a quick update before I hit the sack, a small release with a bug fix and couple of new options. There was a problem with how the number of pages were calculated (it wasn’t including any elements defined inside the pager element rather than in javascript options object) which caused a couple of knock on problems, that I’ve fixed.

New options include the ability to set loading text and page suffix and prefix both for all pages and individual pages. The new linkOverflow feature lets links from linkPagesBefore, After, End and Start to overflow to the other side of the current page if they aren’t all used up. This means that as you get to the end or beginning of the pager, the number of visible page links stay consistent.

Check out the change log for more info, and I’ve updated the documentation to cover these new features.

The first of what I plan to be many updates, hit the link to get a list of changes.

I have done any work on the ajaxPager since releasing a very early version last week. Mainly because I’ve been setting this site up, in fact this blog post is more of a test of my site structure than anything else.

But updates for the ajaxPager will be coming soon.