We have a scenario where we would like the editors to have a limited set of capabilities in one module, but more expanded capabilities in another module. I agree that in a commercial module, the module developer probably shouldn't be changing the editor configuration significantly, but in more custom scenarios, having that capability could definitely be useful. That said, the complexity to support that sort of configuration may not be worth the investment.

More importantly, I think the first task needs to be getting the CK Editor totally working for DNN 7.4, before we start thinking about changing the underlying architecture for it. Once that part's solid, we can focus on expanding the provider capabilities.

---

Brian Dukes Engage Software St. Louis, MO 866-907-4002

DNN partner specializing in custom, enterprise DNN development.

 As you can define into detail what CKEditor looks like, what icons to show and what plugins to load, it should not be too difficult to add something to overrule the editor settings from a module. The current provider on codeplex already allows an admin to do that from the settings for a portals / role / page or module.

---