sebtags 1.0 Release Candidate Released
After years of working on my sebtags custom tag set, I think it is now stable enough to put it in release candidate stage. If all goes well, this will exactly match the final release which will come out soon.
After years of working on my sebtags custom tag set, I think it is now stable enough to put it in release candidate stage. If all goes well, this will exactly match the final release which will come out soon.
I have the third beta of my sebtags custom tag set ready now at RIAForge. I spent a lot of time fixing how things worked in ways that I have intended to fix for a long time, but was not properly motivated to do so. Nothing like releasing something to the public to motivate you to clean things up. The code is still ugly, but the functionality is what counts.
I use cf_sebForm for all of my contact forms. Form spam is a constant problem for those forms. So, I set up a generic way to do filtering in those forms and wrote both cf_sebForm and SpamFilter.cfc to follow the same guidelines.
Today I released the second beta of my sebtags custom tag set. The only major remaining work that I should have before the full 1.0 version is cleaning up and adding some default skins.
In my last entry on handing files with cf_sebForm, I ended the entry by saying that the method I had just covered for handling files with cf_sebForm wasn't the one that I actually used. It was close, but a few differences save me some typing.
In my ongoing series about using cf_sebForm, I have so far left out one important feature - the ability to upload files. This is essential functionality whether you are saving a record or sending email.
I saw two blog entries recently (by Ben Nadel and by Mark Mazelin) on generic solutions to automatically send email with a form. This is a common need for a lot of web sites, especially on contact forms. These entries motivated me to show how cf_sebForm handles this.
When I was working on cf_sebForm, I knew that I wanted it to work on any site. That meant that I had to be able to use the same code for different output on different sites. At first all of my forms were tabular, with code like the following:
Although I briefly touched on validation in cf_sebForm, it is certainly a topic that deserves more attention. This is especially true in light of Ben Nadel's great entry on data type validation versus data value validation (and his final thoughts on the same topic). It is an important distinction and I want to cover how cf_sebForm deals with the challenge.
While working on my custom tag set, I discovered that I often have attributes that will be the same across a whole site. These attributes need to change from site to site.
For example, I have a "skin" attribute to skin the output of my custom tags. Every tag in a site should use the same skin. If I copy some code from one site to another, it should automatically use the skin of the site to which it is copied.