It's a given that DNN core functionality should not be voided by any individual module, and so I suggest returning the ability for the modules to use the host-assigned DNN HMTL editor provider.
The editor is the most significant UI function for users. Websites or intranets with many users will have trained-for and documented, and also customised or developed their own choice of editor providers for DNN, and all modules should insert them wherever the rich text editor is used. This is core functionality and it is the expected behavior.
If this means certain integrated features are not enabled, then that is fine and just a choice to make.
This suggestion does not apply to the HTML Editor module as that is obviously designed to replace the editor. This is meant for all other modules.
Thanks heaps!
References: https://www.dnnsoftware.com/wiki/html-editor-providers https://www.dnnsoftware.com/wiki/modify-html-editor-provider
Robert, The decision was not made out of choice; but rather out of necessity. DNN has been promoting MVC or SPA module development patterns for several years now as WebForms is an obsolete technology. DNN 9 was a big push in this direction with inclusion of Persona Bar and such.
The problem is that the existing HTML Provider in DNN does not support MVC or SPA patterns. DNN has done considerable amount of work within DNN Evoq; but DNN Platform has not seen a way to include DNN HTML provider in SPA or MVC module.
We patiently waited for 2 years. Long story short, we have to support our clients and their DNN versions going back to DNN 7.3. It was necessary for us to adopt and continue innovating. Our HTML Editor is in its infancy but it will get better over time.
Unfortunately, there is no going back to the HTML Provider for our modules. We spent over 18 months in migrating all of our products to new our own HTML Editor (which is powered by the same CK Editor used by the core HTML Provider).
This doesn't seem to be a problem with any of the other modules I use, but in any case, I'll just carry on and try and make the best of this situation. You can go ahead and remove this suggestion from the Ideas log here.
Can you instead please have a look at the last post in my support ticket titled 'Modules no longer using correct editor'? I've asked about setting system-wide defaults for your editor and you might be best to advise.
Thanks Rob
Rob, Setting defaults for the editor has been developed and should be released shortly.
HI Mandeep
Thanks for the update.
Is this going to work in the modules I've purchased e..g. via the common library, or is this only going to work through the separate editor module which I did not purchase?
Regards Rob
Common library update; you do not need to purchase anything separately.
Excellent, thanks for this. I'll get onto that and see how it goes.
Rob
Hi Mandeep
I've got a support ticket in at the moment asking about how to implement this new option to set defaults for the editor that you added. I'm quite certain this was not simply the same customization option that already existed, but I can't see where/how to do it and I don't think I've made it clear enough in my ticket either.
I can of course see the option to create and apply a toolbar to the module or similar modules in the portal, but wasn't there more to this?
Thanks for any further info on this. ROb
From Custom Editor Options > Select Existing Profile > Manage Profile and set defaults.
Ok I see. I thought one would be able to create a toolbar and folder profile to be the default for all portals and all Mandeeps modules on the DNN instance. The point being to not have to set it up fresh every time.
I'll leave that there as a suggestion for future in any case.
hmm I've just noticed there is a file in the portals/_default folder named: Dnn.CKEditorDefaultSettings.xml
That appears to contain editor settings, but it's not clear how or when this file is applied to the editor.
Can I edit this and can I make it apply as the default?
Robert, Different modules use different profiles as their default. For example, to leave a comment in Live Exchange, you don't need the full editor so it defaults to the minimal profile.
You have the option to set the Defaults for all the profile; that should meet your needs. You don't need to set anything fresh every time.
As for creating your own profile and setting it as default for all modules; that will not be supported for the scenario described above. You always have the option to apply a profile to all modules but this of course has to be done every time.