Viewing 9 replies - 1 through 9 (of 9 total)
  • Same issue here. Any way the WYSISWYG Editor inside the admin-panel can be shown in the comment form?

    Found the bug. When TinyMCE doesn’t find the correct language file, it shows the descriptor (“advanced.bold_desc”). But putting a language file in /wp-includes/js/tinymce/langs which corresponts to the language set for your blog. Like if WP has the German locale de_DE, a de.js file should be placed inside the langs folder AND ../plugins/tinymcecomments/settings.js should be configured for the same language as well, like language: 'de'

    Not sure if that applies to everyone, but it worked for me!

    err, object81, in case you are still around – I do not HAVE a settings.js in my plugin folder…
    make a new one and just put in one variable, or how is this supposed to work?

    I can’t get this plugin to show anything else but the dreaded placeholders, and besides looking ugly, it messes up some functionality, e.g. you can’t assign a target when adding a link (actually you can assign it, but it won’t work…)

    Thanks for any more detailed instructions!

    New versions of TinyMCEComments don’t have a settings.js.

    Simply rename wp-includes/js/tinymce/langs/wp-langs-en.js to wp-langs-[YOUR LOCAL].js and edit the labels. I.e. wp-langs-de.js

    Do you have any idea how to fix this in 2.8.4? Renaming the file didn’t work. Thanks in advance.

    Renaming the wp-langs-en.js to wp-langs-[YOUR_LOCALE].js as explained by object81 above is only the first step. Then you have to edit the file and replace all occurances of ‘en’ with [YOUR_LOCALE]. You’ll find them at the beginning of each definition, i.e.

    tinyMCE.addI18n({en:{…

    tinyMCE.addI18n(“en.advanced”,{…

    tinyMCE.addI18n(“en.advanced_dlg”,{…

    tinyMCE.addI18n(“en.media_dlg”,{…

    tinyMCE.addI18n(“en.wordpress”,{…

    tinyMCE.addI18n(“en.wpeditimage”,{…

    Then you may translate the texts as you wish.

    Hi Stefan, even the new version didn’t fix the problem. My wp-langs-de.js does not look like yours. Here’s the beginning:

    tinyMCE.addI18n({de:{
    common:{
    edit_confirm:”Do you want to use the WYSIWYG mode for this textarea?”,
    apply:”Apply”,
    insert:”Insert”,
    update:”Update”,
    cancel:”Cancel”,
    close:”Close”,
    browse:”Browse”,
    class_name:”Class”,
    not_set:”– Not set –“,

    I confirm StefanMz steps, working fine on wp 2.7.1 and TinyMCEComments 0.4.8

    Jani Uusitalo

    (@jani-uusitalo)

    I solved this by modifying the plugin so that it utilizes the core WordPress translation of TinyMCE. Thought I’d link it here to make it easier for others who want to address the problem in this way.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘No tool-tips for WordPress TinyMCEComments on 2.7.1’ is closed to new replies.