Thread

Hi all,

I did talk to the devs on this and they are aware of the problems and are working to sort it out.

I’m going to move this discussion to Community Help since we won’t have a resolution here. The fix will be in a future release, but I don’t want to lose this conversation.

Cheers!

It’s been 3 months since this bug was identified. I am using 2.5.2 and this bug still persist. Is it me?

Yep, if anyone is interested in the progress of this bug, please follow the bug report here.

I just added a +1 to that bug report.

It seems that there are two bugs :

1) When you hit enter on your keyboard the javascript creates a new paragraph whereas it should add a linebreak on the first hit and replace the line break with a paragraph on the second hit

2) When you edit the code (view code button) to add the line break and save, it gets saved but when you save it at a later date the line break disapeers.

in system/expressionengine/module/rte/ft.rte.php comment out line 165

/*$data = str_replace('
', "\n", $data); // must happen before the decode or we won't know which are ours */

Hans-Jakob

As of EE 2.5.5, this is now in system/expressionengine/module/rte/libraries/Rte_lib.php

Hans’ solution is not working for me. What’s the status of the bug and what can I do at this point to get the line breaks to display in the HTML? Thank you.

EE 2.5.5 here and the bug STILL persists. 

Converts my HTML pasted directly into code view from:

<b>“When Earth’s Last Picture is Painted”

Kipling</b>

and creates this hot mess:

<b>“When Earth’s Last Picture is Painted”</b><b>




Kipling</b>

... and on top of it still renders it all on a single line when outputted.

Thought I’d add in my 2 cents… running 2.5.5 on a brand new site/install; still problems with break tags disappearing.  Appears in the RTE source code, but in the page’s output source code there’s no break tags whatsoever;

This is the first line.

This is the second line.

And no break tags rendered.

Pretty useless. What’s the deal EllisLab!?

Same problem for me on a new install. How can this thread be nearly a year old and this not be fixed? Really, guys. We paid money for this.

This bug is aggravating. I can’t pass this off to a client now without a third-party WSYWIG. I certainly can’t expect a client to go in do their listings in HTML in order to get the expected formatting.

Has anyone found a fix for this?? Extremely annoying.

Hey there hilengineering. This is actually fixed in the most recent release. Give 2.6.1 a try and see if that doesn’t clear it up for you.

This doesn’t work in version 2.6.1 either. :-(

Mind posting a new bug report on this with as much clear detail as you can provide? If you’ll post exactly the steps you have to take to see the bug’s behavior, that’ll help us reproduce the bug on our end and get the problem knocked out. Thanks!

Extremely frustrating that such a basic and necessary (mandatory) feature takes so long to get fixed.  I would expect 1000 apologies and a DIY solution posted from the guys a EllisLabs within minutes of discovery.

Hans’ solution worked for me, but was found in the following file around line 419:

system/expressionengine/module/rte/libraries/Rte_lib.php

Just comment out the line:

// $data = str_replace('
', "\n", $data); // must happen before…