I've searched the forums and it seems this is a problem for a couple dozen other people.
I don't want CKEditor to convert angle brackets to character entities when switching to SOURCE mode and using the documentation and browsing the forum I haven't been able to have much success. It also POSTS the data like this no matter which mode I am in, which is a problem as well.
I have tried solving this problem by putting this code in the config.js file:
config.htmlEncodeOutput = false;
config.entities = false;
config.entities_greek = false;
config.entities_latin = false;
Nothing has happened. I've tried setting these in the code and it didn't work either:
<script type="text/javascript">
CKEDITOR.replace( 'message', {
filebrowserImageBrowseUrl : '../ckeditor/Browse.jsp',
filebrowserWindowWidth : 100,
filebrowserWindowHeight : 100
});
CKEDITOR.config.height = 500;
CKEDITOR.config.htmlEncodeOutput = false;
CKEDITOR.config.entities = false;
CKEDITOR.config.entities_greek = false;
CKEDITOR.config.entities_latin = false;
</script>
Here are other people having the same issue, so is this a bug or am I doing something wrong?
viewtopic.php?f=11&t=18974&p=49959&hilit=config.entities#p49959
in config.js file prevents the default behavior, that is transforming greek letters to html entities. However in my case nothing has happened, anyone answering this, is welcomed. I don't want to revert to TINYMCE module. I also tried the above with the prefix CKEDITOR.
waiting for your help and your valuable help
Re: Disabling HTML Character conversion... broken?
Could You provide us some samples?
Re: Disabling HTML Character conversion... broken?
Re: Disabling HTML Character conversion... broken?
Re: Disabling HTML Character conversion... broken?
Bumping the tread isn't going to fix it.
No one understands why this is a problem.
HTML angle brackets _always_ become entities when they are typed into an open WYSIWYG mode instance.
That's the way a WYSIWYG editor works.
Posting :
into an instance which is in source mode won't work either because it looks too much like a HTML tag and the editor will convert it to entities after deciding it is invalid.
At a wild guess on the actual expression you need to pass :
Re: Disabling HTML Character conversion... broken?
I'll take a look at the plugin and that config option and see if I can fix it. Using a mark down editor won't work because the people who are going to use the editor don't know HTML, they just know how to use those specific tags we have.
Re: Disabling HTML Character conversion... broken?
<john black="" white="" >. Any help is much appreciated