Readers fields, don’t ya just love ’em.  They are great when they work properly and if you stick to a few simple rules they normally work with no problems.

1. Never use common names in a readers field.
2. Never mix Users / Groups or Roles in a single readers field.
3. Remember that the server must have the OU/O structure as the user.

Why do I currently hate readers fields?  Well try getting them to work in an R5 environment that has a hierarchial server structure and flat user structure.  Two of the rules are broken immediatly so you explain to the customer that it’s not a supported environment.  Then they point you to a second database where they work fine.  I can’t find out why . . .

Just to let you know that over the weekend I am changing the sites DNS configuration.  The new domain will be http://blog.dnaware.net and it should be active very soon.  I’m using Register365 here in Ireland to register the domain and then I’m setting up ZoneEdit to make all my zone changes.

I’ve gotten ridden of the Java Applet that is used for comment engine so feel free to post loads more comments 🙂

My next trick is to replace the referrer logs with a Top 20 Referrer Chart.  As I get more referrals from a single site it will climb the chart.  Sounds like fun, should be easy to do, just replace the agent so that it increases a counter if there is an existing referral from a site or create a new doc if it is a new referral.  I’ll add this to the coming soon list. . .

UPDATE: The referrer charts are now in place. Lets see what happens…