Thread

I have a field with type Textarea (Rich-Text) selected.

Originally I was having issues with disappearing spaces around anchor tags, but I was able to fix that by adding this code to line 81 of the file ft.rte.php as instructed in another forum post:

'text_format' => 'xhtml',

However, after that, when the field is rendered in the template it adds an additional empty paragraph tag

I’ve seen lots of posts complaining about this but none of the solutions offered seems to work.

Can we get a clear answer as to what is causing these bugs and how to fix them?

Forgot to mention I’m running EE version: 2.6.1 - not many plugins, Structure, low-reorder, etc.

Check out this thread in regards to your spaces issue - I’m not sure about the empty paragraph tags though. I have the same problem and it’s driving me mad.
http://ellislab.com/forums/viewthread/235649/

EE 2.6.1

I’m having a similar problem, although I’m not getting paragraph tags, I’m getting like 4 paragraph break at the end of the text. The RTE isn’t usable this way. I did check out http://ellislab.com/forums/viewthread/235649/ and that solved one problem, but this other issue just isn’t good….

Anyone from EE looking into this?

Ok this is driving me crazy now - I literally change the text and Submit the form to update the entry and it strips out my P and BR tags by the time it’s showing me the changed preview window!  I then click “Edit This Entry” to find my code has been removed and make the changes again, only to lose them once more.

PLEASE PLEASE - anyone have a fix for this or I am just a screwed Core user?

Same problem here. Still after patch it adds empty paragraphs. Unusable for clients.

I know nothing of ‘patches’.
But I think it is really strange that the native EE RTE solution just inserts

after each field in my template. It brakes my design, client not happy.
I’ll look for another solution, but that costs, although little. But still, hard to sell to my client.

Is this being solved soon?

Do the tech of EE read this forum?

Having the same problem here. Any movement on this?

I don’t see any movement on this issue unfortunately — though I wish there were!

In the meantime, since I had a project I had to finish, I started using Expresso which is reasonably priced and seems to do the job for me.

But really, I wish someone at Ellis Lab would browse through now and then just to give an update at least on this issue. I mean, it is a commercial product with a broken piece….

Thanks for the heads-up, strudel. We’ll look into it right away.

** Edit: See below for a better solution **

I’ve had this problem on 2.6.1 as well.  I fixed it by going into /system/codeigniter/system/libraries/Typography.php and changing line 236 from:

$table['##'] = ' ';

to

$table['##'] = '';

I give no guarantees that this won’t cause any unforeseen problems!

I wasn’t really happy with my way of doing it above (1. it felt like fixing the problem but not the cause and 2. I didn’t know what else might be using that function), so I traced it back to where the call for that function is made and made to following change:

In system/expressionengine/libraries/EE_Typography.php on line 407 change

case 'xhtml' : $str = $this->auto_typography($str);

to

case 'xhtml' : $str = $this->auto_typography($str, true);

By passing true in, we’re telling it to remove empty lines.  This isn’t like trimming it however, it will also remove empty p tags in the middle of a field, so if you rely on that for layout, this won’t help you.