Support/Comments for TinymceWrapper

I don't understand what it means to not replace the default file image TV button. If I read this correctly you're saying that entering "NO" retains a button (method) from MODX Native. What is the "file image button" and how is the native button different from Roxy's? Sounds like a big deal if many of us might 'cherish' it.

If I read this correctly you're saying that entering "NO" retains a button (method) from MODX Native.

I'm not sure if something is misconfigured in my test system, but when trying to use the elFinder, one or more URLs seem to be explicitly called using HTTP, which causes problems when the MODX Manager is called via HTTPS. Can you confirm this?

There is no trace of hard-coded HTTP in elFinder environment that I can find.

Please report what file(s) the browser is rejecting

[[~[[TinymceWrapperGRF? &knownField=`pagetitle` &kF=`pagetitle` &kFv=`tw_elfinder_browser` &gNuFv=`id`]]? &scheme=`full` &rememberLastDir=`1` &defaultView=`icons` &unlocked=`1` &theme=`windows10`]]

[[~[[TinymceWrapperGRF? &knownField=`pagetitle` &kF=`pagetitle` &kFv=`tw_elfinder_browser` &gNuFv=`id`]]:replace=`http://==https://`? &scheme=`full` &rememberLastDir=`1` &defaultView=`icons` &unlocked=`1` &theme=`windows10`]]

TinymceWrapper Plugin uses GetResourceField to grab the url of your elFinder resource. Since I don't know if you have friendly url on or not, I had no choice. Please replace this in your Plugin property, enter the url of your elFinder resource.

Most probably the snippet is causing that hazard.
Note: you are suppose to change that value to something real, and not generated by the snippet. The snippet is a mere hack to find the url of your file

RE: samg

I don't understand what it means to not replace the default file image TV button. If I read this correctly you're saying that entering "NO" retains a button (method) from MODX Native. What is the "file image button" and how is the native button different from Roxy's? Sounds like a big deal if many of us might 'cherish' it.

file/image TV button is that button rightmost of the TV input text field that enables you to insert said images and files from file browser to the TV input - which later on shows the thumbnail.
The original button is for the native MODX browser

replaceDefaultFileImageTVbutton
But it so happens that you might be using a custom file-browser (eg elFinder) while editing your resources' content, and you want the same feel of browser for TVs, elFinder would pop up instead of MODX native.
replaceDefaultFileImageTVbutton is for custom browsers to interact with TVs.

Please set replaceDefaultFileImageTVbutton to NO since this is the cause of your erstwhile annoyance

If I read this correctly you're saying that entering "NO" retains a button (method) from MODX Native.

You have never been more exact in correctness!
NO will leave MODX' native bahaviour alone in the regard of TV file/image browser

The only thing that comes to mind is that I never changed the Roxy configuration of "files_root". I left it at /assets. Do you think this is the problem or is something else amiss?

The only thing that comes to mind is that I never changed the Roxy configuration of "files_root". I left it at /assets. Do you think this is the problem or is something else amiss?

That issue is very odd. Some heavy caching issue or server jailer going on.
Is it only elFinder that redirects back to http?

• The MODX Browser works as expected.
• The Responsive FileBrowser shows 403s for the images, but otherwise works as expected. I can preview the images, so this shouldn't be too difficult to fix (maybe something in my .htaccess - /assets/thumbs doesn't exist otherwise).
• Roxy Fileman works as expected, though it starts in its own upload folder and doesn't show the existing files. It's a matter of configuration.
• elFinder is the only one that causes some more severe problems, as reported.