\nTinymce.init function \nA selector (this can be any valid CSS class or id). \n\nHere’s an example of what can go wrong and how to fix it:\n\nDid you catch the other error? The init function was not entered correctly, on top of the open script tags:\n\nChecking the init script for syntax errors is the first step. If that wasn’t a fix, move on to typos and syntax errors within the init script itself.\nTinyMCE not working as a result of typos and syntax\nYou might find TinyMCE isn’t working, even though you’ve configured the tinymce.init correctly. Check through how you’ve typed out each value within the init script. At the risk of overloading you with advice, do these checks as well:\n\n\nAlways place a comma after each value. This is easy to miss when you have a lot of content in your init script.\n\n\nFollow one of the three standards to configure a list of TinyMCE plugins. There are three ways to include a list of plugins:\n\n\nAn array of strings: plugins: [ ‘powerpaste’, 'image', 'help', 'wordcount' ]\n\n\nA space-separated string: plugins: 'powerpaste image help wordcount'\n\n\nA comma-separated string: plugins: 'powerpaste,image,help,wordcount'\n\n\n\n\nAs for the first situation, look at this code snippet. A missing comma after a value is what’s gone wrong here:\n\nThe “height: 600” value is missing its trailing comma, and causing TinyMCE to not work. A text editor with a JavaScript linter installed picks up on these typos. For those of you not using a text editor, look into text editors. They have plugins that can save time debugging, formatting, and writing boilerplate.\nWith these typographic errors covered, next check on where your scripts are placed to get TinyMCE working.\nInline mode activated?\nWhen inline mode is on, but TinyMCE isn’t working, check the element you’ve selected to be a rich text editor.\nTinyMCE inline mode only works on HTML elements other than the