Andrew - I think you're correct. In looking at the code just now, when a custom config is deployed it is written into the "config" table. What's odd is that there are no methods to delete configs. Maybe just an oversight?
Tom - this is most likely the source of your problem. Look at the config table in your Db and delete the offending configs.
The current config table has been an "interim thing" for some considerable time now :) We're hoping to make it a bona fide content type, provide versioning, audit etc for config changes. Just been a bit swamped. But it is on the radar definitely.
-- 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] Aussie Macromedia Developers: http://lists.daemon.com.au/
