Hi
I recommend you seriously consider the Telerik Editor component instead of the FCK editor.
check out this page http://demos.telerik.com/aspnet-ajax/editor/examples/default/defaultcs.aspx
I see many advantages in this editor, for example the W3C scanner, easier spell-checker integration irrelevant of the browser or browser settings and better performance as a whole.
Developer forum
E-mail notifications
Telerik RadEditor instead of FCK editor
Hans Ravnsfjall
Posted on 23/10/2009 11:48:00
Replies
Nicolai Høeg Pedersen
Posted on 23/10/2009 13:20:44
Know the RAD editor - it is really nice.
We have actually been looking at implementing that editor - there are some technical issues though, but I promise we will put some effort into trying to migrate to this editor.
Regards Nicolai
We have actually been looking at implementing that editor - there are some technical issues though, but I promise we will put some effort into trying to migrate to this editor.
Regards Nicolai
Posted on 18/03/2010 10:29:21
As long as all an editor to is post text content to the database, what is the problem with supporting multiple editors.
I notices WordPress supports endless editor variations through plugins.
What stops you from putting in different editiors as a module type. Perhaps even support content editors as custom modules?
I notices WordPress supports endless editor variations through plugins.
What stops you from putting in different editiors as a module type. Perhaps even support content editors as custom modules?
Nicolai Høeg Pedersen
Posted on 18/03/2010 10:58:31
It would be relatively easy to put in another editor and have it work or make it plugin based.
Some features of Dynamicweb would not work though, causing a lot of disturbance in our end. Things lik eInternal links, links to files, stylesheet in editor, the styles from stylesheet should be available, different editor configurations, spell checking, frontend editing etc etc would not work or only partly.
Bu it is on my agenda and it will be done... Good idea to make it plugin based, and that would be the way we would go when we upgrade the editor.
Some features of Dynamicweb would not work though, causing a lot of disturbance in our end. Things lik eInternal links, links to files, stylesheet in editor, the styles from stylesheet should be available, different editor configurations, spell checking, frontend editing etc etc would not work or only partly.
Bu it is on my agenda and it will be done... Good idea to make it plugin based, and that would be the way we would go when we upgrade the editor.
Posted on 07/04/2011 13:17:59
Hi Nicolai,
Is this something we could expecto for Dynamicweb 8 or upgrades of the editor have been solving the major issues?
Nuno
Is this something we could expecto for Dynamicweb 8 or upgrades of the editor have been solving the major issues?
Nuno
Nicolai Høeg Pedersen
Posted on 07/04/2011 13:39:11
Editor was updated with 7.2 - not to Telerik though.
What are major issues? (And will Telerik solve it or just be another editor with the same issues)
What are major issues? (And will Telerik solve it or just be another editor with the same issues)
Posted on 07/04/2011 17:51:53
Hi Nicolai,
The major issues I was talking about was the error reported of the previous versions, stuff like placing br's in firefox, and some bug with the source code that happened every now and again when pasting some HTML.
I noticed the updates and will be looking out for this. I was just asking because you said it was a possibility.
The great advantage in Telerik is table management, the properties inspector, and whole lot of features that make content management a bit easier. I understand though, it's not an easy task in the backend.
Nuno
The major issues I was talking about was the error reported of the previous versions, stuff like placing br's in firefox, and some bug with the source code that happened every now and again when pasting some HTML.
I noticed the updates and will be looking out for this. I was just asking because you said it was a possibility.
The great advantage in Telerik is table management, the properties inspector, and whole lot of features that make content management a bit easier. I understand though, it's not an easy task in the backend.
Nuno