Hi there, This error was encountered by the person in this post http://ellislab.com/forums/viewthread/73184/ but that got marked as solved because of other details that were solved so I am creating a new post about this bug (?) here. It does seem that the LG TinyMCE WYSIWYG editor will sometimes convert linebreaks in the HTML source into in the page display. I tried the solution offered of changing the custom field to textarea and the “Default Text Formatting for This Field” to NONE and then set it back to WYSIWYG again but it didn’t work. Then I created a whole new field and applied WYSIWYG to it and that one is working fine. The first field I applied the TinyMCE to was the default Body field… could this be why it isn’t working? I’m attaching documentation of the form with the 2 fields with the WYSIWYG applied to them, and the same piece of HTML entered into both fields. You will see from the screenshot of the preview, that the same code gets rendered first with a linebreak, and then without. Can anyone help?! Thanks!
I’m running the latest version and build of EE (1.6.4, 20080808), LG TinyMCE (1.3.1), and TinyMCE (3.1.1) and am experiencing this issue. I tried Victor’s procedure (above) for fixing this issue without success. Any ideas?
It looks like TinyMCE is actually adding the additional code. If I save an entry that doesn’t have the extra spaces it still views fine on the site. But, the next time I load that entry for editing, I have extra paragraphs and linebreaks.
Update: It must have been something with the TinyMCE config. I had been using settings from the first-party TinyMCE extension, and when I reverted to the settings that are included with LG TinyMCE the issue is resolved.
I’m having the same problem - create an entry with no <br>s in the post (in either WYSIWYG mode or when you click on the HTML button to view the source), but when you view the live page, extra <br>s and sometimes extra empty paragraphs are being inserted. This happens when creating the entry the first time; I don’t have to go back and edit like cosadmin.
I posted a question on the TinyMCE forum and the only response I got back was that it ‘sounds like a server-side issue’. I’m using TinyMCE 3.2.0.1 and LG TinyMCEe 1.3.1.
Anyone else got any insight into what might be happening?
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.