Answers.Body: <p>You're right, it was a bug. Here's a fix for 4.7.</p>
  
  <p><a href="https://github.com/civicrm/civicrm-core/pull/7438" rel="nofollow">https://github.com/civicrm/civicrm-core/pull/7438</a></p>
  
  <p>The code in 4.7 is a lot cleaner than 4.6; I don't think fixing it in 4.6 will be a priority for the core team.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-12-12T01:17:12.473Z
Answers.LastActivityDate: 2015-12-12T01:17:12.473Z
Answers.UserDisplayName: Coleman
Body: <p>Have shown this to be the case on 2 sites. First site reported the problem and were using TinyMCE. Second site was using CKEditor had no such problem. I then set their wysiwyg to TinyMCE and bingo replicated problem. Can't replicate on Demo as demo user is missing permissions to edit Message Templates.</p>
  
  <p>My search on <a href="https://issues.civicrm.org/jira/browse/CRM-15278" rel="nofollow">JIRA</a> found this which may be an earlier example of the problem, but perhaps it has come back to life</p>
  
Tags: <tokens><message-templates><wysiwyg><tinymce>
Title: Is 'insert tokens' broken for TinyMCE when creating templates
ThreadText: # Is 'insert tokens' broken for TinyMCE when creating templates
  
  (Asked by: username_0 on 2015-12-11)
  
  Have shown this to be the case on 2 sites. First site reported the problem and were using TinyMCE. Second site was using CKEditor had no such problem. I then set their wysiwyg to TinyMCE and bingo replicated problem. Can't replicate on Demo as demo user is missing permissions to edit Message Templates.
  
  My search on [JIRA](https://issues.civicrm.org/jira/browse/CRM-15278) found this which may be an earlier example of the problem, but perhaps it has come back to life
  
  **Tags:** tokens, message-templates, wysiwyg, tinymce
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-12-12. Score: 1 | Accepted answer
  
  You're right, it was a bug. Here's a fix for 4.7.
  
  <https://github.com/civicrm/civicrm-core/pull/7438>
  
  The code in 4.7 is a lot cleaner than 4.6; I don't think fixing it in 4.6 will be a priority for the core team.
  
  
  ---
  
  