An Appeal for Updating and Compatibility

Can anyone confirm the TinyMCE version used in the MODX add-on? I'm not sure but it would seem it's not the current version (4.1.7) http://www.tinymce.com (they look completely different).

If it's not current then is anyone here actively working on updating it for MODX, specifically for use on the front-end with NewsPublisher? Of the hundreds-of-thousands of (MODX) Tiny add-on downloads and all the MODXers using it, I'm surprised there isn't a more vocal majority pushing for an improved add-on. It's an RTE, arguably the most used add-on of any CMS.

There appears to be some slick Tiny plugins like the über-cool Responsive filemanager http://www.responsivefilemanager.com but they seem dependent on Tiny v4. But plug-ins aside, the current MODX version of Tiny feels (and looks) pitifully archaic. I'm no fan of Wordpress but at least their version of Tiny feels modern and is more easily implemented for front-end use.

I want to continue using MODX (and NewsPublisher) for a membership site but I'm really let down and frustrated by such incredibly limited RTE options (with file upload capability) for front-end use. Look, I realize most people here don't require a front-end RTE (be it Tiny or any other) but even so, I'm sure everyone would appreciate an update to the Tiny add-on.

I have a growing concern that if the RTE situation doesn't improve I may need to rebuild the site on a different platform, and I really do not want to do that for a variety of reasons, least of all for a better RTE experience.


[ed. note: todd.b last edited this post 11 years, 7 months ago.]

At Frontend you can use any richtext-editor, which you like.
I like ckEditor in inline-mode for frontend.

You can also use a jQuery RTE in the front-end, there's quite a number of them but 2 good ones are:

https://mindmup.github.io/bootstrap-wysiwyg/
http://markitup.jaysalvat.com/home/

TinyMCE 4 is underway and should be ready soon (days maybe). It's an entirely new project: https://github.com/modxcms/tinymce-rte

I should say, that we're in need of people to help take on and improve extras. We're looking for volunteers to adopt some of the extras we have as managers or integrators. Especially for some of the more popular extras that were developed by @splittingred.

@Jay Gilmore
That's great news. I hope it will be compatible with NewsPublisher.

@Bruno17
I too prefer CKE, though I've never used it as you describe. As it's been explained to me by BobRay, currently NewsPublisher only works with Tiny so CKE is out for now. From what I've been told it seems the file upload mechanism is the biggest hurdle in getting any RTE to work with MODX on the front-end. But perhaps I misunderstand the problem, or solution.

@Dan
I agree there are many nice RTE options, but the problem is getting them to work with NewsPublisher and/or solving the file upload API issue.

Unfortunately I don't have the technical skills to manually replicate the functionality NewsPublisher offers so I pretty much have to use it, and by extension Tiny also. If I were as knowledgeable about MODX as many of you are I'm sure I could build what I want without relying on NewsPublisher. Then perhaps my RTE options might be greater, or not, I really don't know enough about it. Ultimately it seems I'm hampered by my ignorance of how MODX works under-the-hood so I can only use what's within my grasp.

Thanks to all of you.

Regards [ed. note: todd.b last edited this post 11 years, 7 months ago.]

One issue with using the MODX file browser for managing files on the front-end is that it requires certain Manager-level permissions, and a context of 'mgr'. There are a few people working on front-end file managers, but as far as I know nothing actually working yet.

I was lucky enough to have Markus Schlegel contribute to getting a file browser working in TinyMCE with NewsPublisher, for both image and file TVs. It was quite difficult and I don't think I could have done it myself.

The file browser is definitely the stumbling block to getting other RTEs to work in NewsPublisher. I wish it were simpler, since I'm not a big fan of TinyMCE myself.

Here's hoping the new v4 Tiny @Jay mentioned above works with NP. If it doesn't I'll have to rethink a lot of work.

I, like many, hated wysiwyg RTEs, but then came TinyMCE 4, which blew my mind. I can arrive at my goal perfectly with this RTE - best for controlling user input.

I hope the new MODx TinyMCE will not be as dreadfully integrated as the previous. Please, please, please leave 99.5% of TinyMCE alone, at least for the sake of those who choose CMSs because of RTE.

My meaning is, TinyMCE is a full blown, thoroughly maintained and documented third party app with no hope of dying soon.
So, the MODx user, especially the newbie, should not be tied with a second noose (only one is enough), or else, he/she will have to study TinyMCE as itself, and then study TinyMCE as destroyed by MODx.

The integration ought to be done in a way the user can update/customize the third-party thing whenever with breeze ease.

Case in point, the current MODx TinyMCE, the most downloaded add-on in MODx repo, receives one billion complains, simple complains: how do I do this, how do I do that - simple things that TinyMCE website/documentation clarifies, but upon integration with MODx, not a single file can be found for serious customization.
It's almost like ATandT phones messing up stock android, thus having late updates/fixes, non-smart behaviour, etc.

My solution for this was to create my own TinyMCE manager backend plugin. I have not posted it because it is still in trial.
This plugin leaves all the TinyMCE files intact. It uses chunks and system settings to call and bind TinyMCE to this or that rendered doc or chunk form.
And because I have no skill in figuring out the MODx file browser, I use Responsive Filemanager.

In conclusion, unless I am grossly wrong, the only major work is to write an add-on for TinyMCE, for browsing MODx files and inserting them into the textarea; the rest of TinyMCE should be left alone.

Thanks for listening.

Well said, @donshakespeare.

For being the most downloaded (and I assume, most used) add-on in the MODX ecosystem, everything about it's development and implementation feels fractured to me. The roadmap for a MODX/Tiny union desperately needs to be completely reimagined and made clear ... and fixed.

Like @donshakespeare I wasn't a big fan of RTEs either, least of all Tiny. When I started using MODX I was appalled at the available options. Then danyaPostfactum released the lovely CKEditor which looked and worked great and later the guys at modmore reinvented redactor. No, the file browser of either does not (currently) work on the front-end with MODX, but both are still great options, and best of all I could ignore Tiny.

Then I started using NewsPublisher and had to reluctantly accept Tiny as the only option. The other day I visited the Tiny website and was shocked by what I saw: a beautiful (almost elegant) and very functional Tiny. Then @donshakespeare pointed me to the Responsive filemanager plugin for Tiny, all of which threw into sharp contrast what a mess the MODX add-on really is.

Putting Tiny aside for a moment, I do hope other RTE devs will seriously consider making their RTE fully compatible (file browser) for front-end use with MODX. It would be very nice to have more options for those of us using NewsPublisher or for anyone who needs to access the MODX file browser from the front-end.