New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrating TinyMCE 4 #61
Comments
waiting for moxiecode team to release some IE fixes and home to bundle version 4 soon. |
+1 CDN support. Hope to see this soon. |
+1 for CDN support |
just an update, i've started preparing tinymce4 but there are alot o backward incompatible changes |
@aljosa I'm up for testing if you need, why dont setup a branch to take a look? |
@camilonova there is a tinymce4 branch but currently i've just removed v3.5.8 static files |
@aljosa jumping on it, i'll let you know what i get |
There was a lot of chages to be made, so by now i make it work by hand, notice there is also need to change things on filebrowser as well, what i think can be useful is:
But the url in there is hardcoded, we should find a way to use {{ url }} as you did on As is it works, but the filebrowser window gets a couple of JS errors so i could not go further. Hope it helps somehow. |
hello, i'd like to use version 4 without image upload support, |
@caesarsol tinymce4 will introduce a lot of backwards incompatible changes so i'm delaying integration. also, new django-tinymce release should fix problems with CDNs, compressor and language preferences. please understand that delay in supporting tinymce v4 is based on some production issues, backwards incompatibility and my lack of time. |
thanks, i'm looking forward to use the new version in my project! |
I think that the backward compatibility is not more important than the new features of tinyMCE 4. The new version is greater than ever. |
Is tinymce4 branch available for production? |
@tbazadaykin short answer is no. |
Thank you for this great application. Have you made any progress on integrating TinyMCE4? The tinymce4 branch seems to have disappeared from your repository. |
@benoitbar it's https://github.com/aljosa/django-tinymce/tree/tinymce4 |
@aljosa I'm trying to get the tinymce4 branch working with django-cms, I've pip installed that branch, but I get the following javascript error and the editor is not rendered. Uncaught TypeError: Cannot read property 'add' of undefined 127.0.0.1/:229 Here is the code, starting with line 220. It seems the ed.onNodeChanged property is undefined at that point. // Creates a new plugin class
tinymce.create('tinymce.plugins.CMSPluginEditor', {
init : function(ed, url) {
// Register an example button
var tiny = ed;
var c = new TinyMCEPlaceholderBridge(tiny);
PlaceholderEditorRegistry.registerEditor("body", c);
ed.onNodeChange.add(function(ed, cm, n, co) {
var is_plugin = n.nodeName == 'IMG' && n.id.split("plugin_obj_").length > 1;
cm.setDisabled('editplugins', !is_plugin);
cm.setActive('editplugins', is_plugin);
}); |
@mhall119 tinymce api changed in v4.x: are you sure it should work? |
@aljosa I'm using your tinymce4 branch of django-tinymce, so it should work with tinymce 4.x API shouldn't it? |
If people are interested on porting django-tinymce to TinyMCE 4, feel free to help. |
Hi, We have been using tinymce4 with django-tinymce for almost a year now. It's stable and has no major issue. What can we do to speed up the release. We would love to stop pulling it from git every time. |
We have many proposition for that:
|
Note that we will need to make sure tests and documentation are up-to-date. |
I would tend for option 1 as there might still be people using the legacy version. The Documentation is kind of cut/paste from the old one except for a few details (e.g. profile) and a big link to tinymce4 documentation. We could do that. When you say tests you mean automated tests? |
pypi has an option to hide releases so you could in theory deploy new release (django-tinymce==3.x) to pypi and hide it. |
actually if they froze correctly their settings there should be no problem even if 3.x is not hidden |
I have interest in getting TinyMCE 4 support, and willing to spend time help with development / testing. |
I am working right now on integrating the latest version and update the documentation. Will post my work soon. But, I never contributed to an official project ;-) what I am supposed to do? Pull request?
|
So I have locally upgraded tinymce to 4.2.4, extended the documentation (the part that took some figuring out few months ago) and bumped the version. I have installed it locally and tested it within our application and seems fine. |
Pull request is there. |
Fixed with #128 |
Actually I didn't noticed that the PR was on tinymce4 rather than master. |
We will need to prepare a clean merge for tinymce4 and master before going forward. |
Ok I'll merge and prepare a pull request on master |
I just sent a pull request for master I tried my best at merging them but they were quite different.. I tested it briefly in my application to see if everything was still working compared to tinymce4 branch and it seems ok |
Any news on this? We can also fork the tinymce4 into a new project and take it from there... |
It sound a reasonable choice to me. |
Should I do it or you want to do it? |
If you feel like maintening it you are most welcome 👍 |
I have no idea if I will be able to, lets see... For now I will fork it adjust the comments and links to the right repo and post it to pipy as django-tinymce4 |
Feel free to add @aljosa and I to the contrib of your repository. |
of course |
done and submitted to pipy, already available online as django-tinymce4. Enjoy |
Youhou, great. |
For me, django-tinymce4 on pypi / the tinymce4 branch didn't work. It seems unmaintained, eliminates features I need (such as TINYMCE_JS_URL), and I believe sure has some issues with newer versions of Django. See this Pull Request for an alternative: #239 |
Hi,
Has anyone attempted to integrate the latest TinyMCE build into django-tinymce? I've currently been giving it a go, but the settings for relative_urls seem to be ignored, and my URLs are not building correctly.
If anyone else is working on this, maybe we can work together to get this up and running? Or are there plans to upgrade at a later time?
Thanks!
The text was updated successfully, but these errors were encountered: