TinyMCE config errors

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
7/18/2015 5:21:07 AM
Gravatar
Total Posts 115

TinyMCE config errors

Hi Joe

I was trying to work out why a site using TinyMCE refused to allow links to open in a new window (bearing in mind your opinions on this subject ;-), and found a small config error. This line in mojoTinyMCE4.config has typos highlighted:

ExtendedValidElements="iframe[src|width|height|style|name|title|align|scrolling|frameborder|allowtransparency],meta[itemprop|content],link[itmeprop|href|class|onclick],a[itmeprop|href|class|onclick]"

And to permit the target attribute (which seems polite given the editor allows the user to specify this for a link):

ExtendedValidElements="iframe[src|width|height|style|name|title|align|scrolling|frameborder|allowtransparency],meta[itmeprop|content],link[itemprop|href|class|onclick],a[itemprop|href|target|class|onclick]"

7/20/2015 12:41:58 PM
Gravatar
Total Posts 18444

Re: TinyMCE config errors

Thanks for the bug report and provided fix! I have pushed this fix into our source code repository.

You must sign in to post in the forums. This thread is closed to new posts.