The documentation isn't great here, after searching for a couple hours I came across this line you can add to your config.js to stop <p> tags from automatically being added in new line breaks.
config.enterMode = CKEDITOR.ENTER_BR
There really isn't a great solution without heavily modifying the editor. I'm running into all kinds of issues, automatic wrapping of elements with <p> tags, code indentation and breaks... basically destroying my markup.
It'd be great if these settings could be set with a GUI so that the developer can choose how code should be formatted.
I've been struggling with config.entereMode for a few hours now and am not having luck getting the editor respect my choice (config.enterMode = CKEDITOR.ENTER_DIV).
I'm playing with the samples and have tried the standalone config.js, the core/config.js and repackaged, cleared browser history, etc. Not having much luck. I even put some alerts() in and do see the config.enterMode showing as 3 (CKEDITOR.ENTER_DIV), but the editor still throws in <p> on key.
What I've noticed is that if the textarea is primed with something like:
<div>test div</div>
Then, subsequent enter keys generate a <div> - regardless of the enterMode setting.
Similarly, if the textarea is loaded with something like:
<p>test para</p>
Then, subsequent enter keys generate a <p> - again regardless of the enterMode setting.
If the textarea is blank, it always uses a <p>, regardless of setting.
The enterkey sample provide with the distro does work, but I can't seem to get things to work without having to destroy and perform CKEDITOR.replace again.
Not critical, but thought I'd share my experience. If anyone has a surefire way to get <DIV>'s generated on enter -- regardless of existing content -- then I'd sure appreciate some hints.
Re: Do not include <p> tags in body by default
I have created a small function (classic ASP) that strips them from the text before its displayed.
Re: Do not include <p> tags in body by default
config.enterMode = CKEDITOR.ENTER_BR
There really isn't a great solution without heavily modifying the editor. I'm running into all kinds of issues, automatic wrapping of elements with <p> tags, code indentation and breaks... basically destroying my markup.
It'd be great if these settings could be set with a GUI so that the developer can choose how code should be formatted.
Re: Do not include <p> tags in body by default
Here's some more info, you can wrap them with div's instead:
http://docs.cksource.com/ckeditor_api/s ... .enterMode
Re: Do not include <p> tags in body by default
I've been struggling with config.entereMode for a few hours now and am not having luck getting the editor respect my choice (config.enterMode = CKEDITOR.ENTER_DIV).
I'm playing with the samples and have tried the standalone config.js, the core/config.js and repackaged, cleared browser history, etc. Not having much luck. I even put some alerts() in and do see the config.enterMode showing as 3 (CKEDITOR.ENTER_DIV), but the editor still throws in <p> on key.
What I've noticed is that if the textarea is primed with something like:
<div>test div</div>
Then, subsequent enter keys generate a <div> - regardless of the enterMode setting.
Similarly, if the textarea is loaded with something like:
<p>test para</p>
Then, subsequent enter keys generate a <p> - again regardless of the enterMode setting.
If the textarea is blank, it always uses a <p>, regardless of setting.
The enterkey sample provide with the distro does work, but I can't seem to get things to work without having to destroy and perform CKEDITOR.replace again.
Not critical, but thought I'd share my experience. If anyone has a surefire way to get <DIV>'s generated on enter -- regardless of existing content -- then I'd sure appreciate some hints.
Thanks!
Shawn