Buy Now
Sign in

CC6 Rich Text Editor for text areas

mestizero , February 15 2019, 23:18
M
mestizero 10
February 15 2019, 23:18 #383916
Has anyone been able to get the Rich Text Editor feature to work in CC6?
I found a related post here: https://www.chronoengine.com/forums/posts/t104011/html-editor-in-text-area-cc6.
The WYSIWYG interface does not appear when toggled on. And to be clear, I added the Textarea from the Fields dropdown with no luck.
Screenshots of my testing...
Calling the fields
cc6-1.png
First textarea
cc6-2.png
Second textarea
cc6-3.png
The Result
cc6-4.png
healyhatman 9
February 26 2019, 10:10 #384199
If you make a CF FORM with a rich text editor, and then use {chronoform:form_name} it works properly. Otherwise the JS files for the editor are at libraries\cegcore2\assets\editors\tinymce there's bound to be a proper init function in there somewhere. Although it would be nice if it "just worked".
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
admin 32
February 28 2019, 17:49 #384270
 1
Hello,
By default the editor script is loaded by the "form" view, which means that your textarea must be called from a "form" view for the editor to work, do you have the textarea inside a form ?
Best regards
M
mestizero 10
March 01 2019, 19:37 #384323
 1
Hello Max,
Still no luck. I've called the text area from the index event, the form (form19), and from the fields fields (fields20) via custom fields. The text areas are the same from the original example, field_textarea13 has the rich text editor toggled off, and field_textarea18 has the rich text editor toggled on.
Below are screenshots illustrating my efforts.
The index event loads a view of form19 followed by loading the textareas directly. healyhatman's suggestion of calling a Chronoforms form is the last portion of the event, which is a functioning workaround.
thing1.png
Within form19, I call the textareas again, to compare behavior with calls from the event and from within the form. I also reference the form fields fields20, which again calls the text areas.
thing5.png
fields20 uses two custom fields to call both text areas.
thing4.png
Content within the red box is from form19. Content in the green box is the text areas called directly from the form. Content in the purple box is from the index event. Lastly, the yellow box shows the results of the Chronoforms call.
thing6.png
I think I've done every iteration possible, but am happy to continue testing scenarios.
Thanks!
Attachments
thing1.png
thing1.png
(14.83 KiB)
563 Downloads/Views
thing3.png
thing3.png
(42.18 KiB)
546 Downloads/Views
thing4.png
thing4.png
(31.11 KiB)
536 Downloads/Views
thing2.png
thing2.png
(32.96 KiB)
507 Downloads/Views
thing5.png
thing5.png
(23.19 KiB)
542 Downloads/Views
thing6.png
thing6.png
(44.04 KiB)
583 Downloads/Views
admin 32
March 10 2019, 19:28 #384626
How is this working after the new update released today ?
Best regards
M
mestizero 10
March 12 2019, 21:16 #384772
Hi Max,
We're getting closer, but there still some work.
If there is one textarea, then the WYSIWYG editor will appear as designed. If there are several textareas with the rich text editor toggled on, then only the last instance will display the WYSIWYG editor.
On the image below, the rich text editor is toggled on for Introduction, Email Body Paragraph 1, Email Body Paragraph 2, Email Body Paragraph 3, and Email Body Paragraph 4. The Closing Paragraph originally had the rich text editor toggled on, but I toggled it off so u can see the resulting markup language.
Thanks! Hopefully this is an easy fix.
thing7.png
Attachments
thing7.png
thing7.png
(34.11 KiB)
505 Downloads/Views
healyhatman 9
June 22 2019, 03:26 #387705
Hey Max I'm still having this issue. Even a blank CF form with just 3 text areas and only the last will actually have the rich text editor.
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
healyhatman 9
June 22 2019, 03:47 #387706
 1
 Answer
I figured it out though. In libraries/cegcore2/assets/js/g2.tinymce.js in the init function, in the $(selector).each(function(i, textarea)) loop, you need to reset the tinymceSettings var. If you do that, all of the text areas render properly.
That means move the tinymceSettings = { ----- }; line to just inside $(selector).each(function(i, textarea))
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
C
cesarvelame 54
June 01 2020, 16:47 #392883
Can you send your g2.tinymce.js with that tip?
Thanks.
healyhatman 9
June 01 2020, 23:23 #392889
It was a year ago I don't have it anymore. Just follow the instructions
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
admin 32
June 02 2020, 01:25 #392894
this is going to be fixed in the next v7 update!
healyhatman 9
November 29 2020, 04:57 #395084
Hey Max can you put this fix in v6 as well please
Web developer at SkySpider.com.au - I DO NOT work for ChronoEngine!
Donations: paypal.me/healyhatman
Professional Work: kamron@skyspider.com.au
Custom CF / CC Plugins and Extensions: skyspider.com.au/store
admin 32
November 29 2020, 15:02 #395089
I do not think that will be easy to do at the moment!
C
cesarvelame 54
January 06 2021, 20:55 #395584
If someone get the same issue.