While reviewing ticket 20607, an issue was identified related to the behavior of replacement fields in templates when multiple editors are present on the same page.

Background:

Before commit 5f84fe89c50, the first template where replacement fields were correctly displayed and inserted was the Confirmation template. In that context, everything worked as expected.

However, in subsequent templates (such as Registration or Basic Admin Notification), all replacement field options resulted in inserting {TOKEN} instead of the selected value.

After the mentioned commit, the issue appears to have shifted: Replacement fields now work correctly in Invitation and Reminder templates. The issue persists in other templates.

Technical Analysis:

The root cause appears to be within the CKEditor plugin limereplacementfields.

The plugin uses a <select> element with the ID cquestions to list replacement fields.
On selection, it retrieves the value using: $('#cquestions').val()

On pages with multiple editors, multiple elements share the same ID cquestions, which is invalid in HTML.
As a result, $('#cquestions').val() always returns the value of the first matching element in the DOM, leading to incorrect token insertion.

Suggested Fix:

Ensure that each replacement field selector has a unique identifier per editor instance, or scope the selector to the active editor context instead of using a global ID.

Impact:

This affects multiple templates where more than one editor is present, leading to incorrect token insertion and potential misconfiguration of email templates.

Notes:

The issue is not new but was previously limited to specific templates. Recent changes appear to have shifted where the issue manifests rather than resolving the underlying cause.