Closed (fixed)
Project:
YAML Form
Version:
8.x-1.0-beta18
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Oct 2016 at 20:39 UTC
Updated:
8 Nov 2016 at 15:54 UTC
Jump to comment: Most recent
Comments
Comment #2
jrwest_webguy commentedUpdate: Modified the toolbar settings for the 'Basic HTML' text editor -- found at Admin>Config>Content Auth>Text formats and editors -- but they did not transfer over to the 'Settings page' WYSIWIG editors for some reason -- in fact it doesn't look like they transferred over to ANY WYSIWIG editors used by the YAML forms module(s). This despite my 'processed text' element having a drop down to select which (system-wide?) text editor configuration to use.
Comment #3
jrockowitz commentedI am avoiding using 'Text Formats and editors' for basic HTML snippets because I wanted to provide a simpler and more consistent HTML editor. For example, I am not sure how we would handle things like uploaded inline images and embedded media (which are supported 'Text Formats and editors' ) in email confirmations and messages.
I am hoping a compromise might be to keep the simple HTML Editor but allow any tag to be entered via view source mode.
I am going to test CKEditor's config.allowedContent and see if it works as expected.
http://stackoverflow.com/questions/15659390/ckeditor-automatically-strip...
Comment #5
jrockowitz commentedSetting allowedContent to true, now allows any HTML markup to supported by the HTML editor.
Please test the latest dev release.
Comment #6
jrwest_webguy commentedConfirmed: The WYSIWIG editors on the settings page work much better now and will accept the HTML code I want to use there. Thank you, jrock!
Comment #7
jrwest_webguy commentedSorry. When I added my confirmed / kudos, it changed the status to active instead of fixed. Setting it back to fixed now.