I made a minor update to the tag last night. I removed an extra non breaking space I had in one of my preset LayoutNumbers. Since this is a minor revision an update from v1.08 to 1.08a is not necessary, but still suggested.

I want to give a special thanks to all those who have helped to test this last version and to those who have sent in their kind emails. Keep 'em coming.

New version 1.08 (CF_Search_NextPrevious)

I have made a revision to the ColdFusion custom tag CF_Search_NextPrevious. Anyone using v1.03 or newer can just overwrite their old version with this one. The major reason for this version update was to support XHTML. Other new features are listed below.

We had a great time at my family's cottage. Sorry I don't have any pictures... they're still on the camara. Hannah (my 3month old daughter) was a doll and behaved pretty well overall.

Last night I worked on a new beta release for the custom tag Search_NextPrevious (v108 beta 2). I still have heard very little from people testing it. I would really like to hear people's feedback. Please help out if you can.

Changes since beta 1 are:

• minor bug fixes
• Added example 5 to demo (which takes advantage of the two new attributes below. It also demonstrates how you can use a preset stylesheet and still over-ride style classes. This override feature hasn't existed until v1.08b2).
• Added attribute "CurrentPageWrapper_start"
• Added attribute "CurrentPageWrapper_end"

New Version 1.08 beta 1 (CF_Search_NextPrevious)

This revision is still in beta. The main purpose for this revision was to support XHTML. Other new features are listed below.

The demo.cfm file has also been updated to reflect XHTML support. Because I am not an expert on XHTML yet I'd like to hear whatever feedback you have to offer (hopefully not criticism :)

I look forward to people's input and assistance.

New version 1.07 (CF_Search_NextPrevious)

I have made a revision to the ColdFusion custom tag CF_Search_NextPrevious. Anyone using v1.03 or newer can just overwrite their old version with this one. The major reason for this version update was because of user request to have the current page number center properly (like google does).