Quote from: Bruno17 at Nov 11, 2010, 09:54 AM
in your firebug-DOM is the MODx - object there?
I don’t see it.
Quote from: Bruno17 at Nov 11, 2010, 09:57 AM
http://www.revo.webcmsolutions.de/247.html
does mine work for you?
It does. Both sections. I have to leave now, but later, I’ll try to run a diff on the sources. Maybe that will show something.
Quote from: Bruno17 at Nov 11, 2010, 12:11 AM
hmm...
seems /manager/assets/modext/build/core/modx-min.js isn’t loaded.
I don’t have a build directory in /manager/assets/modext/ so those files aren’t there to load. Did you add that dir. or are we just using different versions of MODx?
change
$modx->regClientStartupScript($modx->getOption('manager_url').'assets/modext/build/core/modx-min.js');
to
$modx->regClientStartupScript($modx->getOption('manager_url').'assets/modext/core/modx.js');
in \core\components\tinymcefe\home.php
then it works also in 2.0.5 from git
Thanks. I copied the build directory from a traditional install last night -- that fixed it. I wonder if it should be included there in the Git version?
On another topic: Does it make sense to modify TinyMCE so it works in the front end rather than having tinymcefe as a separate add-on?
If not, I’m wondering if I should package tinymcefe into the NewsPublisher package (as I think you’ve done with your add-on) or if it should be a separate package that can be used by multiple components.
Quote from: splittingred at Nov 12, 2010, 12:36 PM
Quote from: BobRay at Nov 12, 2010, 12:33 PM
On another topic: Does it make sense to modify TinyMCE so it works in the front end rather than having tinymcefe as a separate add-on?
Yes. This is the best route.
I would do it, but my JS fu is too weak.
There seems to be a demand for a Revo version of NewsPublisher among people who want to convert Evo sites and don’t want to switch to FormIt. I have a (more-or-less) working version of NewsPublisher with tinymcefe, but I hesitate to release it if TinyMCE itself will be fixed in the near future. Can you give me any guidance there?
I tried something out on tiny.js, tinymce.class.php, script.tpl to get it work with xdbedit.
At the end I made very,very small changes on them and copied them to my folders for xdbedit.
Then I tried it for you, if this works also on frontend. As it did I bundled them together in tinymcefe for you, Bob, that you have a startpoint.
I can try to find out what we have todo on the original-files, so we can use it for the backend-stuff with resources and for xdbedit and also for the frontend, if nobody else.
Quote from: Bruno17 at Nov 12, 2010, 03:14 PM
I tried something out on tiny.js, tinymce.class.php, script.tpl to get it work with xdbedit.
At the end I made very,very small changes on them and copied them to my folders for xdbedit.
Then I tried it for you, if this works also on frontend. As it did I bundled them together in tinymcefe for you, Bob, that you have a startpoint.
I can try to find out what we have todo on the original-files, so we can use it for the backend-stuff with resources and for xdbedit and also for the frontend, if nobody else.
I think it’s probably up to you unless Shaun has time (very unlikely). I can advise you on using Git to create a pull request with the changes if you need that, but I’m pretty hopeless when it comes to JS debugging. A simple solution to front-end rich text editing would really be great.
I do have everything working in the front end (though I haven’t really tested the operation of TinyMCE). Thanks again for all the work.
