Uploaded image for project: 'CiviCRM'
  1. CiviCRM
  2. CRM-12296

Allow 'new' text in word replacements to accept HTML entities

          Details

          • Type: Bug
          • Status: Done/Fixed
          • Priority: Minor
          • Resolution: Fixed/Completed
          • Affects Version/s: 4.2.8
          • Fix Version/s: 4.3.0
          • Component/s: Core CiviCRM

            Description

            Presently, if you attempt to do a word replacement and enter HTML of some sort (eg. a link), CiviCRM escapes the characters.

            Since word replacements is only ever accessed from the backend, I think it is safe to disable this escaping.

            The attached patch disables HTML escaping for the 'new' field, and also enables support in isSkippedField() for recognising indexed files, eg. new[1], new[2], new[3], etc. This latter modification was required in this instance.

              Attachments

                Activity

                  People

                  • Assignee:
                    lobo Donald A. Lobo
                    Reporter:
                    torrance123 Torrance
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: