[1.5.2] Fix a bug that kept some rich-text fields from saving#4091
Merged
Conversation
Member
Author
|
This was merged without review because it was a hotfix while some of the team were on annual leave. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #4088.
I checked all the places we include JQTE in forms, and made sure they did not interfere with a TinyMCE-powered field. These were the only two problems:
JQTE forms that do not interfere with a TinyMCE field
I checked and cleared these fields:
Out of scope
These fields are not actively used: