Thread

I’m using the new RTE to add & edit channel entries via the front-end.

It appears to work fine when I’m adding a new channel entry, however, when I use the same template to edit an existing channel entry, the WYSIWYG screws up, and displays the raw HTML in the editor window.

Here’s what I see when adding a new entry:

Adding a new entry

Here’s what I get when I open that entry for editing (in WYSIWYG view):

Editing - WYSIWYG view

And here’s what it looks like in Code view:

Edting in code view

The exact same template is used for adding new & editing existing entries.

What’s going on?

Anyone?

Hi Dan,

First of all, let me congratulate you on a fantastic name. I totally approve.

Second, I didn’t replicate your exact issue, but I did find some bugs.

In order to get this exactly right, can you tell me a bit more about your situation?

Were these exiting channel fields that you converted to RTE?

What was the formatting for the Textareas before conversion? Were the set to None, XHTML, etc.?

If you convert them back to textareas, what do you see in the Control Panel edit screen? In SafeCracker?

Can I see your SafeCracker template code?

We’ve definitely found *some* bugs, I just need your help to determine how many. Thanks!

Cheers,

Hey Dan,

Were these exiting channel fields that you converted to RTE?

Yes, actually they were previously textarea fields before I updated to EE2.5 (from 2.4).

What was the formatting for the Textareas before conversion? Were the set to None, XHTML, etc.?

Pretty sure the field was set to XHTML.

If you convert them back to textareas, what do you see in the Control Panel edit screen? In SafeCracker?

If I change the field back to an XHTML textarea, I get the HTML markup in both the CP and Safecracker.

Can I see your SafeCracker template code?

Sure thing:

(note that {field:our_people_bio} is the RTE field)

Just for info, if I create a brand new channel field as an RTE, I get the same problem, so it does not appear to be related to a field’s previous “history”.

Any news on this?

Thinking I’ll just need to cut my losses and ditch RTE in favour of WYGWAM.

Hi Dan,

I’ve brought this up to the Dev team, since I wasn’t able to replicate exactly. They are aware of the issue and are working on it as a bug at the moment.

Essentially, your content is getting “double encoded”, but the Control Panel compensates for this, where SafeCracker does not.

There isn’t a fix available right now, however.

Cheers,

Ok cheers Dan.  WYGWAM it is 😊

Hi Dan,

Thanks for you patience!

We’ll be making improvements to RTE as time goes on. It is definitely a 1.0 product at this point!

Cheers,