If you use an 'Advanced HTML/Text' element in a a webform it doesn't get displayed properly: its (HTML) content is left out. It has a type of 'processed_text' but when Civictheme's 'form-element--civictheme-field.html.twig' is invoked it isn't capable of handling that type.
Add 'Advanced HTML/Text' element to webform and give it some default contents. Display the webform: contents is missng.
Either some extra preprocessing to allow 'form-element--civictheme-field.html.twig' to deal it or an additional
'form-element--civictheme-field--processed-text.html.twig' template that maps it to a paragraph (see example - but I don't know if this would have any unintended side-effect).
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | civictheme-test-webform.png | 2.04 MB | sonam.chaturvedi |
| #8 | advhtml.png | 392.12 KB | sonam.chaturvedi |
| form-element--civictheme-field--processed-text.html_.twig_.zip | 443 bytes | mwjansen |
Comments
Comment #2
mwjansenComment #3
fionamorrison23 commentedHi @mwjansen thanks for logging this issue. We'll have a look at this. We're doing some work on webforms at the moment. we'll let you know if our work will fix the issue you're encountering.
Comment #4
richardgaunt commentedWE are actively working on this branch to create an opt-in system for form element preprocessing rather than the current opt-out.
https://github.com/civictheme/monorepo-drupal/pull/1306
The ck editor webform fields are something we are testing and ensuring are working before we are releasing a fix.
Comment #7
richardgaunt commentedComment #8
sonam.chaturvedi commentedVerified and tested on 1.x-dev
Testing Results:
1. 'Advanced HTML/Text' element in a webform, the text is displayed properly - PASS
2. Webform elements and their respective HTML output correctly on the front-end - PASS
Screenshot:
PFA screenshot of webform with Basic HTML element, Advanced HTML/Text & Horizontal rules.
Comment #9
richardgaunt commentedComment #10
richardgaunt commentedComment #12
fionamorrison23 commented