Este módulo habilita la edición WYSIWYG (“lo que ve es lo que obtiene”) de áreas de texto del OJS mediante el uso del editor de contenido Habilitar ACTUALIZAR MÓDULO ELIMINAR MÓDULO
Su pregunta parece más a cerca de la categoria questions do que una “feature request”, así yo cambié las categorías.
¿Al hacer clic en “habilitar” sólo redirecciona o redirige y habilita el módulo?
¿Podría leer su log de servidor web para verificar los mensajes sobre esa acción y lo que dice su servidor cuando hace clic en el botón habilitar?
====
Your query looks like closer to question than a feature request so I moved to this category.
When you click “habilitar”(enable) button it only redirects or redirects and enable?
Could you check your webserver log to verify messages about that action and what your server says when you click enable button?
Regards,
Israel Cefrin
Public Knowledge Project Team
we had the same problem, and after applying the patch, we can enable or disable the TiniMCE Editor, but when we enter something into WYSIWYG Editor and we save it, it doesn’t work, it doesn’t save anything, unless when we open the HTML Editor, then it save whatever we enter in the textarea.
It occurs with every textarea field, in submission metadata editting and in configuration editing (2.5 for example).
Thank you from now,
best regards
Jose Angel Navalón,
University of Valencia.
Hmmm… Strange… Do you get/see any PHP errors in your apache error log file or any JavaScript errors in the browser web console/development tools?
Hmmm… :-\
The problem was that when I tried to edit some textarea field of the setup pages, with more than one textarea, it only saved the content in the last one.
But other plugins worked fine, like CustomBlock and StaticPages, so, I finally modified TinyMCEPlugin.inc.php to have working the plugin.