How can I convert the textarea to RTE? I tried, but any is added at the parsing template, so the old data is showed as just one big paragraph.
Thanks.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
May 10, 2012 8:45am
Subscribe [9]#1 / May 10, 2012 8:45am
How can I convert the textarea to RTE? I tried, but any is added at the parsing template, so the old data is showed as just one big paragraph.
Thanks.
#2 / May 11, 2012 10:37am
Hi Robson,
Thank you for posting your question here on the ExpressionEngine forums.
Can you tell me a bit about the steps you took to utilize RTE?
I am guessing that you upgraded to 2.5 and then enabled RTE.
Did you edit the channel field so that it is no longer just a plain text area?
Check out the attached image and let me know!
Thank you,
#3 / May 11, 2012 10:45am
Hi again, Shane!
Yeap, I did all this. But, at the frontend, the old content is being parsed without the . I guess, since the RTE field type add the at edition, the old parsing rules don’t apply to them. Am I right?
#4 / May 15, 2012 12:00pm
Hello Robson,
I am afraid I do not quite understand what you are observing.
The conversion to RTE should keep things just as they were.
Can you show me a screen shot of what you are seeing before and after?
Thank you,
#5 / May 15, 2012 12:23pm
I had the same issue and turned off RTE for the fields as a result until I could get to posting here about it.
I’ve attached some before and after shots. (The RTE version image has all the contact info bunched on one line.)
#6 / May 15, 2012 12:30pm
Exactly this! Thanks, Bruce!
I have to go! Bye!
#7 / May 15, 2012 3:24pm
Also having the same exact issue. Even if I go in and update the content to add back the paragraphs (via wysiwyg), it reverts back after I submit. Would it have anything to do with the deprecated
?
#8 / May 16, 2012 5:22pm
Hello mmcgeeCC,
That behavior is intended. We validate against HTML5 and not XHTML.
Thank you,
#9 / May 16, 2012 5:23pm
Bruce and Robson,
Were these just text areas before or were you using a WYSIWYG Add-On before the conversion?
Thank you,
#10 / May 16, 2012 5:28pm
Hi, Shane.
I’m not sure, but I believe
validates on both doctypes. So, looks a better choice.
Back to the old topic, my fields were just textareas.
Thanks!
#11 / May 16, 2012 5:43pm
Mine also were just EE text areas.
#12 / May 16, 2012 5:44pm
I’m having this issue as well. All markup generated by the RTE is tripped on output in the template.
- my fields where never textarea, RTE from the beggining.
#13 / May 16, 2012 6:07pm
This is the code in my field (the RTE content):
<p>CHEF SERIES</p>
<p>47 THE STRAND, PARNELL, AUCKLAND</p>
<p>Ph: +64 9 309 1081</p>
<p>Fax: +649 309 7655</p>
<p><a href="mailto:[email protected]">[email protected]</a></p>
and this is what is output:
<p>CHEF SERIES</p>
<p>47 THE STRAND, PARNELL, AUCKLAND
Ph: +64 9 309 1081
Fax: +649 309 7655
<a href="mailto:[email protected]">[email protected]</a></p>#14 / May 17, 2012 4:50pm
I think I found the problem. JS errors in the template variables accessory(had an old version: 1.1) were stuffing up the RTE in Firefox.
#15 / May 17, 2012 5:06pm
Nope. its still not working as expected.