Comparison of WYSIWYG field values fail because of HTML tags involved

Created on 30 July 2023, over 1 year ago
Updated 4 March 2024, 9 months ago

Problem/Motivation

The WYSIWYG editor form of "Manage dependencies" has HTML tags along with the string value, where as the node WYSIWYG editor does not have the tags with string value. This creates failure in comparing values and does not trigger the action.

Steps to reproduce

For example: When a WYSIWYG type of field - like the standard profile "body" field for example - is used to build a condition based on its content then it fails to trigger. The node type used here is "article".

Proposed resolution

Strip HTML tags so that the "real" content (string value) can be compared.

Remaining tasks

Testing if does affect other scenarios negatively so that we have to discuss another solution.

🐛 Bug report
Status

Needs review

Version

4.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024