Support/Comments for TinymceWrapper

That was months ago!
Months ago, even MODX had issues, lol
And the internet did not work out of the box for some users

https://github.com/tinymce/tinymce/issues/3939#issuecomment-331805567
As of recently, if you are having issues with inserting images from ANY File Browser and stuff into your TinyMCE content area

Temporary fix, until the CDN is fixed as per the official TinyMCE github issue notification

Switch to (Downgrade):
https://cdn.tinymce.com/4.5/tinymce.min.js
(this sticks the CDN to 4+ major version 5)

instead of

https://cdn.tinymce.com/4/tinymce.min.js
(this is always the latest CDN - major 6 and counting + minor V patches)

and you will be fine.

If using TinymceWrapper, change that CDN setting (tinySrc) in your plugin set.

O, what joyous pitfalls there are in the use of CDN JS scripts

- donShakespeare

[ed. note: donshakespeare last edited this post 6 years, 6 months ago.]

Please go back to using https://cdn.tinymce.com/4/tinymce.min.js

https://www.tinymce.com/docs/changelog/
Official TInyMCE Version 4.7.0 October 3, 2017

ADDED new mobile ui that is specifically designed for mobile devices.
Updated the default skin to be more modern and white since white is preferred by most implementations.
Restructured the default menus to be more similar to common office suites like Google Docs.
FIXED so theme can be set to false on both inline and iframe editor modes.
FIXED bug where inline editor would add/remove the visualblocks css multiple times.
FIXED bug where selection wouldn't be properly restored when editor lost focus and commands where invoked.
FIXED bug where toc plugin would generate id:s for headers even though a toc wasn't inserted into the content.
FIXED bug where is wasn't possible to drag/drop contents within the editor if paste_data_images where set to true.
FIXED bug where getParam and close in WindowManager would get the first opened window instead of the last opened window.
FIXED bug where delete would delete between cells inside a table in Firefox.

Revo 2.5.8
TW 2.3.2

I recently ran into an SSL issue with the default TW paths which previously worked perfectly fine.

By default the CommonCode Chunk paths use either,

skin path:
or

external plugins:
The problem is that with SSL the browser blocks these assets because the generated links use 'http' which prevents TW from loading.

Now, I have configured MODX to use 'https' which works great everywhere else (CSS and js files, links etc.) so why it's suddenly not working with these TW assets I don't understand.

I modified the path using

which seems to work, but if anyone knows of another (better) solution I'm all ears.

The older version of TinyMCE used to display a warning when people left the description (alt tag) field blank. This new one doesn't, and I can't find anything online about enabling this warning in the new version. Do you know of a way to require data in the description field?

Quote from: todd.b at Oct 08, 2017, 01:28 AM

Revo 2.5.8

which seems to work, but if anyone knows of another (better) solution I'm all ears.

Does your context have a "site_url" set up for it? If so, does that have the secure address in it?

Hi @rainbowtiger,

No, I have not setup a "site_url" for either the web or mgr contexts for this particular site.

Though I haven't done so with several other sites either, and yet I don't see this TW problem with them so it whatever the cause it must be unique to this site.

RE: rainbowtiger

The older version of TinyMCE used to display a warning when people left the description (alt tag) field blank. This new one doesn't, and I can't find anything online about enabling this warning in the new version. Do you know of a way to require data in the description field?

This is not the place of an RTE, by default. It can be a feature request though - easy to implement!

Few things to keep in mind

1. Do you want RTE on the description field?
2. Do you want the "required" prompt script to be superficial, JS-only or server-side? See examples in:
   https://docs.modx.com/revolution/2.x/developing-in-modx/basic-development/plugins/system-events/onbeforedocformsave

Quote from: donshakespeare at Oct 12, 2017, 09:42 PM

[li]Do you want RTE on the description field?[/li]
[li]Do you want the "required" prompt script to be superficial, JS-only or server-side? See examples in:
https://docs.modx.com/revolution/2.x/developing-in-modx/basic-development/plugins/system-events/onbeforedocformsave[/li]
[/ol]

Sorry, forgot to specify that this is for the Images popup (hence the reference to the "alt" tag), not MODX's "description" field for resources. That's what the old TinyMCE did to assure that all images have alt tags entered.

Task for creative minds:

Can you think of a way to specify different media sources for the insert images popup versus the links popup? Sure would be nice. I have clients who always upload things in the wrong place (images in the documents folder, or documents in the images folder, depending on which media source is defined as the default one in MODX).