Support/Comments for TinymceWrapper

Once you start doing MODX permissions, anything could be the matter - just observe the myriad of forum posts on the subject. You really need to put on your MODX hat for that cup of fish.
And since I can't see what you are doing, it's all guessing from here.
Also, if you are going to configure elFinder for users, it might come in handy to head over to elfinder.org to see how this 3rd-party software rolls.

As for the current integration:

admin account seems to have intermittent upload capabilities

From cache to cookie, and resource groups and session timeouts, I can only say good luck.
Observe the behaviour a bit more and let me know of concrete patterns - so I can better troubleshoot.

I'm not sure if that's just a raw value that hasn't been successfully masked

You are right. Talk to the MODX officers about this issue.
You know how you see a drop list of users to select from, and it's just blinking numbers, then you refresh, then the usernames reappear...that' what is going with the list
Default = forMembers - it's all good, the same the same...no need to change it back and forth

It can indeed, but it'd be great if it didn't require its own separate configuration. Media Sources are intended to be system-wide, but for elfinder I need to set up properties in a rather obscure snippet. (Trying not to sound like I'm complaining!)

I tried, but it was a knavish waste of my precious time.
see my inquiry https://forums.modx.com/thread/86910/modmediasource-object#dis-post-530897
Media Sources are site wide, so are the elFinder settings - two distinct cars parked in the same garage. There is really no need to have the same glove box.
I keep them separate for now, for both lack of skill and lack of interest. I personally have never had any use for MODX Media Sources. They are utterly useless when the native browser is avoided.

I am not altogether certain that the elfinderConnector snippet is obscure

RE: Dave Smith
https://github.com/Studio-42/elFinder/wiki/Connector-configuration-options

location1Path means path = full path = /internet//submachine/ownserver/htdocs/www/public/cloud/assets/thisRuddyFolder/
[[++base_path]] is MODX' idea to cut all that jargon
You need [[++base_path]]assets/ or [[++base_path]]assets/myMedia/

RE: donshakespeare
Thank you!

The trick to working with permissions is a lot of trial-and-error. First make sure that whatever you are doing works fine without any permissions set up at all.

Then create a new Policy that is just a duplicate of the Administrator, all permissions enabled. Attach that Policy to your group and again make sure everything works.

Finally start unchecking permissions, testing after every few that you uncheck, to make sure everything still works.

Once you get it where you want it, and you know it all still works, if you want to you can create a new Policy Template with just those permissions you have enabled in your duplicate, and then assign the new Template to your group's Policy.

Ok, points taken everybody, thanks very much indeed.

I've been sure to remove the resources from the group I've configured, specifically to avoid permission complications. I'm testing with only the admin account, and I'm using the location path: "[[++assets_path]]images/". The path works, I can browse just fine, but when I upload the file appears (near instantly and usually without the "uploading" popup), but doesn't produce a thumbnail, allow me to "get info", or remain after a refresh.

RE: arimanr
I am glad you got it sorted...let me know if TinyMagicPublisher has any issues, thanks.

RE: Dave Smith
I forgot to ask, how are you uploading?
1. Im-mediate Drag and drop works only in latest versions of Chrome and any other browser that is high tech
2. then there is right-clicking on an elFinder folder "Upload files" with fancy pop up drag and drop pop
3. then there is clicking on the toolbar "select files to upload"
If you run into a brick wall, I will you give you 5 minutes free sevice

My problems appear to be solved. Apologies for the running in circles, but I confess I didn't impliment your original changes to the efinder.html source because I imagined you'd publish an update that would render that unnecessary, and so chose to 'patch' by changing the myModxPermissions property in the default set in order to allow uploads.

Having found nothing but strange and inconsistent effects this entire time I decide it would be best to take your recommendation, modify the script to ensure the correct property set was loaded this time, and surprise, surprise, everything appears to be working perfectly.

So all my problems stems inexplicably from the snippet's inability to load the property set correctly using the 'pset' parameter.

I've been able to create a user group for users from whom I wanted to hide the unsightly "TinymceWrapper" resources on the main tree, without interrupting their ability to use them when clicking the elfinder buttons through the Manager. Now it's working, my users won't need to see those in the tree and wonder what they are!

I've now also been able to fully customise the location URLs, eg: [[++assets_path]]images/. Uploading works perfectly in FF, Chrome and IE11, all with d&d. Just lovely.

The only question I haven't managed to answer is, where did those interestingly advanced image editing buttons go?

Thanks, as ever, donshakespeare, for indulging me and being so wonderfully helpful. I'm excited at how this one addon dramatically improves Modx as a whole, significantly improving one of many severely lacking aspects of the system which I otherwise love.

My next challenge is to fix Everett Griffith's addon, "Taxonomy" so I can have proper WordPress-like hierarchical categories for resources.

Oh, but on the topic of Media Sources, while I believe I can see where you're coming from, surely it can't be denied that there's at least one legitimate and important use for them: directing file/image TVs to specific folders to prevent site admins spewing files all over the site root.

With this essentially custom location management, elfinder allows you to access all those locations easily enough, but it doesn't force users to put their blog images in the images/blog/ folder. Of course there's nothing stopping me continuing to use Media Sources on TVs, but I'd like one day to be able to tell Modx to show either the default file browser, or elfinder as the browse tool for TVs, where at present it seems there must be both.

It's not always a clean or complete solution, but the FileUpload snippet will let you direct uploads to a specific directory with a property (that could come from a TV, a User Setting, or a Group Setting).

RE: Dave Smith
Thanks for reporting, very helpful!

Next release will have an option to destroy the default TV file browser button, just as presently you have the option to hide the default top nav MODX native browser link, when you have a custom browser in action.
I agree this eliminates comfuzchion.

but it doesn't force users to put their blog images in the images/blog/ folder.

With elFinder, you will be surprised what you can do. This request is easy peasy. Ever heard of elFinder's startPath? You can dictate where exactly your users go.

The only question I haven't managed to answer is, where did those interestingly advanced image editing buttons go?

I dunno, man! I used Google image search to find possible elFinder imagetools, nada! nihil!
Dreaming is good, but it was only a dream! Only I myself am crasy.

My next challenge is to fix Everett Griffith's addon, "Taxonomy" so I can have proper WordPress-like hierarchical categories for resources.

Someday ... I'll head that direction