This conversation sparked some notion of de ja vu... so I thought I'd ramble a bit about this issue:

Just as an aside on Containers in 1.0.1 - you can always use the undocumented containerid attribute of the cfa_container tag - but this does mean that you will have to plan out what containers you want, and some how administer these id's amongst your other site developers. Using this ID instead of the container name became much more manageable as it stopped the problems of duplicate and empty containers being created for the same page.

At an old place I used to work, we built a little wizard to help you create a container, by firstly asking the user what they wanted to call their container, and then let them know if one already existed with that name and provided them options such as delete and create new etc... once created, the container id was returned, and another screen allowed you to look up all of the available containers etc... i took the concept a little too far and wrote a "container health analyser" that reported the status of all of the containers, those that were empty, those that had no rules, those that had invalid buffer descriptions etc..." - you could remove all of the problem containers quite easily and everyone was happy - it worked well in 1.0.1 but was obsoleted with the improvements in 1.5.

Pete

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To Unsubscribe visit http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a message to spectra-talk-request@houseoffusion.com with 'unsubscribe' in the body.