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.

Comments are great for making sense of code, they’re also really handy for debugging. By “commenting out” code you can prevent it from being from run without having to delete it.

Doing this for a single line is easy peasy just stick you cursor at the begining of the line and tap / twice.
doSomething();
becomes
// doSomething();

However commenting out multiple lines is a bit more of a pain: click at the beginning,insert /*, click at the end insert */.

Recent I discovered a way to do this really quickly in Coda, just select the code you want to comment out, hold down cmd and press /. You can also go the other way, just make sure you selection starts at the /* and ends at the /* and it will remove the comment for you.

Despite one rather strong recommendation against it I’ve moved digitalintuition.co.uk over to 1&1 from Media Temple and things are much much quicker. Still lots to do, but you should see more happening here now.

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.

I’m off to Chicago on Saturday, for a couple of days training with Ex Libris on our new Library System and how to make it look nice and pretty. I’m also taking the Mrs and have a few days leave tagged on to the end of my trip which I’m really looking forward to.

Got loads planned, hopefully we’ll be able to fit most of it in, especially looking forward to going to a Chicago jazz club, trying a Chicago style pizza and Viva! the latin music festival, which just so happens to be on while we’re there.

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.

I was playing around today with Symfony (1.2.8) and Doctrine (1.0) and I was trying to add a custom field to one of my model classes. I followed the Doctrine documentation on adding a custom field, and all I got was “Unknown record property” exception. I’m going to go through the whole process but if you just need the solution to the problem jump to here.

Now my example was more complicated than this but I am going to use the example in the Doctrine documentation as it’s easy to explain and you can compare it to what they’ve written. Basically I wanted to add a field to my model object that didn’t exist as a database column. For example if you have a users table with a first name column and a last name column and you want to be able to find the full name with out combining these two each time. So you need a custom full name field.

The Doctrine documentation says you need to create  an event Listener for when the object is hydrated (when data is loaded from the database into the object).

class HydrationListener extends Doctrine_Record_Listener
{
  public function preHydrate(Doctrine_Event $event)
  {
    $data = $event->data;
    $data['full_name'] = …