I've had similar issues but I think if fckEditor didn't put those darn <p> tags around content automatically, the issue would go away and it would make things easier on many fronts. I have sites where I have used the Content Template feature to allow users to bring in a page headers and some boiler-plate text. The template works fine but after it is saved, fckEditor adds those darn <p> tags and the user has to go in and remove them from the source. I have used fckEditor in other apps and it does the same thing so I think it is a problem with it and not mojo. If that is the case, not much can be done from the mojoPortal point-of-view so I guess your suggestion is the answer.

-Joe D.

I read this post and spent the last few hours looking into how to make the FCKeditor not put that <p>&#160;</p> in there (instead of what I planned on working on  ;-))

What I found was a way to solve it in IE but not other browsers.

By changing the /ClientScript/mojofckconfig.js like this:

FCKConfig.EnterMode = 'br'; // p | div | br
FCKConfig.ShiftEnterMode = 'p'; // p | div | br
FCKConfig.FillEmptyBlocks = false ;

(Whereas previously EnterMode was p and ShiftEnterMode was br)

I now get different bahavior in 3 browsers.

IE does what I want and puts nothing in there.

Chrome puts &#160; but no more <p>

Firefox puts a <br /> there

weird!

I chased all around the javascript trying to figure out if I could fix it tobe the same in other browsers but have not been able to figure it out and giving up for now.

So my question is should I keep these changes and have different behavior in different browsers or switch it back so its consistently <p>&#160;</p> in all browsers? Opinions?

Best,

Joe

I'm inclined to agree its better to keep it the same in all browsers. Users can override it using a custom config file for FCK anyway if they want to.

Most editors do use p for enter and br for shift enter, problem with FCKeditor is its putting that in when we haven't typed anything.

So one possible solutions is I can check if the content starts with <p>&#160;</p> and remove it using server side code when it is being saved. I guess the thing is to try adding an image, does it put it inside the <p> or after the <p>&#160;</p>, if the latter this strategy may work but if the former it won't.  Just need to experiment and see what actually happens.

Best,

Joe

Hi Joe,

No you've spoken it just the way I grok it. If not for the pesky p tag that FCKeditor insists on wrapping things in then there would be no need at all for an Image Module, we could awlays just use the Html module since it already has the ability to browse and upload images, the only pesky part is having to train users how to work around the FCKeditor issue by going to source view removing the wrapping p and saving without switching back to wysiwyg view. So the html module can be used today as an image module its just this pesky problem that takes an expert or some training to work around.

I think the future is the new CKeditor, but it doesn't have the image browse and upload stuff out of the box like FCKeditor I think because thats how he's trying to make his living by selling the add on CKFinder. Once I can figure out how to make my own .NET upload/browse dialog that can work with CKeditor then I will focus on it going forward and hopefully they will or have solved this issue.

Best,

Joe