I am amazed how Drupal add TinyMCE as a module!

Hi all,
I am done with this TinyMCE Wrapper, but have spent overly seasoned hours on packaging the blasted thing, still with packaging errors ( running 2.3.5)
I am currently at serious odds with Packman and ThemePackagerComponent.

I battled through MyComponent, but I think I need fresh eyes to enter a brawl with that powerful beast.
I know MIGX has something of the sort, but why on this brown young earth is it impossible for me to find?

For now I think I am just going to toss the bits on Github

@BobRay
Are you speaking of Image TV or/and File TV, where the user can browser server files?

As for media source, Responsive FileManager exposes its 'upload dir' logic quite beautifully. With some lines of code I reckon it will be easy to check the user's permission policy and thus provide the media source url accordingly. [ed. note: donshakespeare last edited this post 9 years, 5 months ago.]

Okay, finally got ThemePackagerComponent to work; well no readme, I guess it will prove intuitive.
It has been submitted to the MODx Extra joint...waiting for approval

Here is a tutorial if you are in a hurry to build this awesome stuff:
http://www.leofec.com/modx-revolution/tinymce-wrapper-for-modx-manager.html with Github links and all.
I don't know if it is permissible to attach a transport package here.

Enjoy

It looks very cool. What happens if the user has the traditional TinyMCE package installed?

This plugin comes in disabled so as not to invade the user's experience.
This plugin can be deactivated in two ways, both of which render it quite useless.
Deactivate the plugin as plugins are deactivated.
Turn on the deactivate option in its script properties.

If this plugin is activated in both ways suggested above, it will always override any other RTE selected in the System Settings which_editor, and turns on the use_editor.
Of course this behaviour can be destroyed by commenting out that line of code controlling it.

And since TinyMCE is mere JavaScript, that is client-side, the code in any one of the chunks can be used to attack any RichTV textarea that is exposed by Newspublisher. And yes the Responsive FileManager works out of the box in the frontend, as well as the backend, with or without TinyMCE or Newspublisher.

I came close to getting the MODx File Browser to work, but alas...that kettle is whole different level of fish.
Next battle is with Image TV and MIGXs

https://github.com/donShakespeare/tinymce_wrapper with link to download [ed. note: donshakespeare last edited this post 9 years, 5 months ago.]

Yes, image and file TVs were a big hassle in NewsPublisher.

Is the stats high for those who require Image /File Tvs in the frontend?

This should be mighty easy for you to do (ahem, not so much for me). Have you looked in TinyMCE link or image plugin?
These files are located within the plugins folder. On their Git page they have unminified versions.
There is also the small responsivefilemanager(tinymce bridge) plugin which acts like the above.


All we want is, to grab plain text from the file browser and dump it in the textarea (stripped of all html, onsubmit/save).

Now these plugins already do something of the sort, when you proceed to insert media....we need to clean that up and transform
Or simply stop the plugin from wrapping it up in the first place.

My head already hurts

Don't those plugins require Manager access credentials?

No, the TinyMCE plugins are agnostic to location, and since the main TinyMCE is accessed via CDN, the plugins can be anywhere.
I will look at this method later on for backend integration, or just go the simpler route listed below.

I worked out Responsive FileManager, thanks to its excellent demo page and Newspublisher's exposing of all things exposable.
This is now fully compatible with Newspublisher: Rich TVs, Rich Textareas, File/Image TVs

For File and Image TVs (frontend) - no Manager credentials needed whatsoever!!!!
-Open Newspublisher's npFileTpl, then replace [[+npx.browserUrl]] with
/your-assets-url/components/tinymce_wrapper/responsivefilemanager/filemanager/dialog.php?type=2&popup=1&field_id=[[+npx.fieldName]]&fldr=/

-Open Newspublisher's npImageTpl, then replace [[+npx.browserUrl]] with /
/your-assets-url/components/tinymce_wrapper/responsivefilemanager/filemanager/dialog.php?type=3&popup=1&field_id=[[+npx.fieldName]]&fldr=/


Gradually saying goodbye to MODx' File Browser.
Next on agender are the mysterious Media Source api, Dropbox, Amazon bucket and whatnot

@donshakespeare was nice enough to give me a pre-release heads-up on the TinyMCE Wrapper which I installed yesterday. He also helped me with some custom tweaks for my NewsPublisher/membership needs.

First off, the ability to cut the cord between NewsPublisher and TinyMCE is f-a-n-t-a-s-t-i-c. I removed all RTE-related properties from the NP call and can easily customize every facet of Tiny whether for the Manager or NewsPublisher, with the convenience of loading it from a CDN. It offers a nice sense of integration when editing on the front and back that was missing previously.

As someone else mentioned previously the use of Chunks may not be ideal (I really don't know) but it's certainly easy to use. I can adjust Tiny on a field-by-field basis, front and back. How cool is that? But for me the best part is having access to the Responsive Filemanager in the Manager. This is great news. It offers a much nicer user-experience than the default file browser, plus I like the fact that whether I'm using NP to edit or the Manager I get a similar user-experience.

@donshakespeare has done great work with TinyMCE Wrapper. This is a pretty big deal, especially if you also use NP.

It would be great if this concept could be applied to other RTE and/or file managers.

Thank you very much @donshakespeare.

https://creativ.space [ed. note: todd.b last edited this post 9 years, 5 months ago.]