I'm using WYSIWYG with TinyMCE. It works well, but I'm having a problem when I make line spaces. Then TinyMCE inserts <p>&nbsp;</p>. When I save it, &nbsp is removed and ; is left and visible. Does anyone know what could have caused this? I tried disabled all filters, the problem still persists.

Comments

TwoD’s picture

Input filters do not affect how TinyMCE or any other editor behaves, they only run during rendering.
Does the source look ok if you disable rich text editing? What you see there is what will be submitted to the server.
Are you using any plugins provided by other modules or the bundled Teaser Break module?

Toxid’s picture

The source looks okay when I disable rich text. This part <p>&nbsp;</p> is sent to the server and this part <p>;</p> is rendered. I have the Teaser break plugin for TinyMCE activated, but the problem persists even after I deactivate it. I'm clueless of what it can be.

TwoD’s picture

And the source is still ok if you go back and edit the node?
If the source is ok and it happens during rendering, it's got to be one of the filters doing something weird.
What filters do you have installed, except for the Core ones?
Disabling them all should have solved the problem and provided a clue to which one it is.

Toxid’s picture

Exactly my point. When I go back to edit the node the source looks as it should. I've disabled all filters, both input formats and TinyMCEs filters. I'm going to start disabling modules now.

EDIT: I've found out that it's a theme related problem now. It doesn't appear in Garland. I will probably find the culprit soon now that I know where to look. Thanks for trying to help!

sun’s picture

Status: Active » Fixed

Sounds like Wysiwyg is not the cause.

Toxid’s picture

WYSIWYG was not the cause. It was theme related. I found this in my preprocess node function:
$vars['content'] = str_replace('&nbsp','', $vars['content']);. I don't remember why I put in that code, I just removed it and everything worked properly.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.