There is no need to change any config etc for this new release and there is a tag for this release in the SVN so you can use Tortoise SVN to diff from previous releases.

This is still a bug:

Using SVN 21/2/2008

In Fullscreen edit mode, hit Preview - path gets lost - gives error showing wrong path to example.html - path starts at site root and does not include the URL base e.g. http://mysite.com before the path.

In normal view, hit Preview - All OK

We have them up and running at the example pages. You need a pretty new version of the ImageManager the latest 3.0.6 is verified to work with both TinyMCE 3.0.1 and TinyMCE 2.1.3 so if you have that one it should work just fine.

That's exactly what I'm getting with the ImageManager 3.0.6.

I installed TinyMCE 3.0.1 and the ImageManager 3.0.6.  When I click on the image icon in TinyMCE in Firefox, I don't get the little icon on the right of the image path input of the pop-up window. In IE, the icon shows up in the pop-up window but when I click on it, the ImageManager loads forever and get a javascript error:

Line: 161
Char: 4
Error: Object doesn't support this property or method
Code: 0
URL: <baseurl>/tiny_mce/plugins/imagemanager/pages/im/index.html

More results from some debugging.  The ImageManager 3.0.6 in standalone mode works if I don't load the TinyMCE 3.0.1 javascript before the ImageManager javascript.  As soon as I load the TinyMCE 3.0.1, I get the JS errors and the ImageManager doesn't work.

Here's what I include at the top of my page to configure TinyMCE and the ImageManager to be used on the same page as a plugin and in standalone mode.  This worked perfectly when I was using TinyMCE 3.0 and ImageManager 3.0.5.  All I did when I installed 3.0.1 and 3.0.6 copy the new files over the old install...also updating the config.php file in the tiny_mce/plugins/imagemanager directory.

I double checked that the tinyMCE.init({plugin : "imagemanager"}); is in my config...  As mentioned above, this configuration worked perfectly...

<script language="javascript" type="text/javascript" src="../sources/jscripts/tiny_mce/tiny_mce_gzip.js"></script>
<script type="text/javascript">
        tinyMCE_GZ.init({
    plugins : "safari,table,save,advimage,advlink,insertdatetime,preview,flash,searchreplace,contextmenu,paste,fullscreen,spellchecker,noneditable,visualchars,nonbreaking,xhtmlxtras,imagemanager",
    themes : "advanced",
    languages : "en",
    disk_cache : true,
    debug : false
        });
      </script>
      <script language="javascript" type="text/javascript">
        tinyMCE.init({
        plugins : "safari,table,save,advimage,advlink,insertdatetime,preview,flash,searchreplace,contextmenu,paste,fullscreen,spellchecker,noneditable,visualchars,nonbreaking,xhtmlxtras,imagemanager",
        mode : "textareas",
        theme : "advanced",
        width : "100%",
        theme_advanced_blockformats: "p,div,h1,h2",
        theme_advanced_styles : "Warning=warning;Nav=article_navigation;Nav Title=article_navtitle; Thumbnail Link=thumblink",
        theme_advanced_buttons1 : "newdocument,|,preview,|,spellchecker,|,cut,copy,paste,pastetext,pasteword,|,undo,redo,|,link,unlink,anchor,image,cleanup,help,code,|,search,replace,|,removeformat,visualchars,visualaid",
        theme_advanced_buttons2 : "styleselect,formatselect,|,bold,italic,underline,strikethrough,|,justifyleft,justifycenter,justifyright,justifyfull,|,bullist,numlist,|,outdent,indent,|,sub,sup",
        theme_advanced_buttons3 : "fullscreen,|,forecolor,backcolor,|,charmap,|,tablecontrols",
        theme_advanced_toolbar_location : "top",
        theme_advanced_toolbar_align : "left",
        theme_advanced_statusbar_location : "bottom",
        theme_advanced_resize_horizontal : false,
        theme_advanced_resizing : true,
        apply_source_formatting : true,
        plugin_insertdate_dateFormat : "%Y-%m-%d",
        plugin_insertdate_timeFormat : "%H:%M:%S",
        extended_valid_elements : "iframe[style|src|frameborder|width|height|align|scrolling],object[type|data|align|width|height],param[name|value],a[class|name|href|target=_blank|title|onclick|rel],img[class|src|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name],hr[class|width|size|noshade],font[face|size|color|style],span[class|align|style]"
        });
      </script><script language="javascript" type="text/javascript" src="../sources/jscripts/tiny_mce/plugins/imagemanager/js/mcimagemanager.js"></script>

Last edited by caz (2008-02-21 20:49:07)

Woohoo. Thanks for the fix.

Hi!

Just updated tinyMCE in my CMS from 2.1.3 and so far it looks good. I just have one feature request: Could the domain relaxing be made even a bit more relaxed? Or is it possible to disable it completely?

My setup is that I have multiple domains running on the same server, with the static files being served from a dedicated vhost for all of them. So I would be fine if the domain checker would only compare IP addresses, but right now, opening popups (like advanced color picker) always results in JS error messages.

Hello
I've added tinyMCE 3.0.1. It works great on Firefox but can not display in IE6!! Is there any mistake or wrong config I've made?

Hi!

@spocke: I had the setup working with tinymce 2 and a lot of other javascripts, and tested it in IE6,7 FF2, Konqueror and Safari 2,3, and never had a problem with loading script files. Interestingly enough, a custom plugin I ported over from tinymce2 is still opeing its popup correctly, but the built-in ones like colorpicker throw errors and display empty popups.

These are the errors firebug reports for colorpicker:

Illegal document.domain value" code: "1009

this.params has no properties
getWindowArg("plugin_url", undefined)tiny_mce_popup.js (line 47)
requireLangPack()tiny_mce_popup.js (line 98)
[Break on this error] var v = this.params[n];

@spocke  It appears to be an issue with loading something via ajax.  The comments we use load after the page loads via ajax and this is when the issue happens.  If I change the comments from ajax to flat loading (i.e. put into the html directly) it works like it should.  If I change it back to the AJAX loading of the comments the error shows up again.  This does not happen in 3.0.0 so something was changed with how the DOM is being read or something I cant put my finger on it right now as I dont have the time look for it.  But perhaps Tiny is unable to find the id of the item I am asking it to replace.  I did see however that the style is never changed on the textarea to display:none; when a textarea is trying to be replaced that was loaded via ajax.

Ok sounds good.  Do you guys have an eta on the next minor release?