For a current project the client is using facts, links, and a custom banner system we built (will share when done). The client has specified they do not want to editable rules for these features, but rather, they want the system to display dynamic content automatically based on the categorization tree.
I assume you mean you effectively want a hardcoded container that just spits out dynamic content with unchanging parameters. I guess I'd normally think about sticking that in the template inside a custom tag designed for the job.
[Or hardcoding a container name -- and having admin responsible for updating the container. We're looking at a revamped container model to make things like central management of named containers possible.]
Basically, I took some code from the random fact rule and put together a CFC that only asks the uses what dynamic content to show in a given place (but I may even have to remove that).
A CFC would be fine. But anything going in a template that a client might want to modify we try and keep to custom tags. They're just easy for Dreamweaver types to understand. Of course the tag could call a CFC ;)
I updated the SQL to compare the keywords associated to a given piece of dynamic content to the teaser and meta content of a given page, then to display the dynamic content based on a match.
One of the nice things about categorisation is that you only need to do a simple join to pull back the data you need. We've been looking at building an API that means you don't have to write your own SQL statements -- which is a good thing for cross db compatability etc. Time, time, time... :)
Does this sound reasonable?
Sounds great. Look forward to setting up a "Developers Exchange" when all these custom objects and rules come flooding in ;)
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
