-
-
Notifications
You must be signed in to change notification settings - Fork 818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Surveys: Fix I18n translation support and WYSIWYG support #26135
Surveys: Fix I18n translation support and WYSIWYG support #26135
Conversation
…be a RichTextEditor for the translation given it is already a wysiyg in singlelingual mode
(Standard links)
|
Ah if I go back and edit the spanish now the english is html. So it's not being racist it's that there's some double escaping going on. |
hmm that does feel strange maybe something in the way the l10n form saves? |
@demeritcowboy I believe I have found the problem see civicrm/civicrm-packages#361 |
Correct me if i'm wrong, but I tweaked the PR title because it helps with release notes. (I haven't tested yet, but sounds like a good catch) |
The addition to skipfields seems to make it work without needing the packages PR. I don't see any other fields in core called "instructions", so there's no conflict. And it would likely be a wysiwyg if there were one added somewhere. Out-of-scope:
Also not a blocker for this PR: The ThankYou message on petition is translatable, but is html code in a regular textarea in the popup. So am going to merge. |
The "instructions" field is already a wysiyg in singlelingual mode.
Overview
This allows for the user interface to update the translation for the instructions field
Before
Database is translatable but UI does not support it
After
Both DB and UI support translating of the field
Technical Details
Note that on the form https://github.com/civicrm/civicrm-core/blob/master/CRM/Campaign/Form/Survey/Main.php#L126 https://github.com/civicrm/civicrm-core/blob/master/CRM/Campaign/Form/Petition.php#L174 it is already a WYSIWYG which means that RichTextEditor is the correct widget to use not TextArea
ping @demeritcowboy @eileenmcnaughton @mlutfy