TinyMCE Browse button doesn't work

TS672
Windows Server 2003
Tested in both Firefox and IE

We have TS672 installed on our development server and it's configured to use TimyMCE. I'm trying to insert an image or link in a TinyMCE field in a DCR and nothing happens when I click the Browse button. I don't even get an error message, even if I have that option turned on in the IE settings. I couldn't find anything in the forums specifically about the Browse button not even responding, so I'm wondering if it's a configuration issue on my server or if it's a browser setting imposed by my company's security settings. Has anyone ever heard of this or know how to fix it?

Find more posts tagged with

Comments

Slabrador

We have TS672 installed on our development server and it's configured to use TimyMCE. I'm trying to insert an image or link in a TinyMCE field in a DCR and nothing happens when I click the Browse button. I don't even get an error message, even if I have that option turned on in the IE settings. I couldn't find anything in the forums specifically about the Browse button not even responding, so I'm wondering if it's a configuration issue on my server or if it's a browser setting imposed by my company's security settings. Has anyone ever heard of this or know how to fix it?

Which version of TinyMCE are you using? (TS672 has v2, TS672 patch 1 has v3.)

I would be surprised if this was caused by a sectuity setting as you're not browsing the local machine, you're browsing the TS workarea. You're sure that you're not getting any errors at all in FF JS error console?

Could you post your custom_config.js so we can see if anything stands out there?

JessicaD

Hi,

We're using version 3 (TS672 patch 5811). I checked the FF error console and I'm seeing a series of css errors for dialog.css and iw.css and a couple of JS errors that say "f is undefined." The link for the JS errors take me to line 7381 in tiny_mce_src.js:

return f.apply(s || t, Array.prototype.slice.call(arguments, 1));

I opened a case with Interwoven to see if support can help. So far they've said my custom_config.js file looks correct, but I attached a copy anyway.

Slabrador

OK, I haven't looked at the js file just yet, but 'f' is usually defined as the form on the dialogue page, so I'm guessing that you're probably missing

var f = document.forms[0];

at the start of your init and / or insert functions in dialogue.js.

I'll let you know if I spot anything in custom_config.js.

Slabrador

In your plugins list in custom_config.js you have advimage and advlink - replace those with iwimg and iwlink and ditch

IWTinyMCECustomConfig("ceridian","file_browser_callback","iwBrowse");

That worked for us (we're also on TinyMCE v3)

JessicaD

Making that change worked and allows us to use the standard image and link buttons, but we were hoping to have the advanced features available. I searched for dialogue.js on the server's hard drive, and there were no results. I'm beginning to think that it wasn't installed correctly.

Slabrador

Sorry, my mistake, it should have been dialog.js - the example plugin has a javascript file called dialog.js and that's what we've based all our custom plugins on, so I pretty much forgot that the JS used by the dialogue can be called anything - these JS files are always in <iw-home>/httpd/iw/tinymce/jscripts/tiny_mce/plugins/<pluin-name>/js.

I don't think there's a problem with your install, I think it's just a case of getting your head around TinyMCE - I banged my head on the desk quite a few times getting to grips with it.

Anyway, it sounds like you're making progress - making that change worked and allows you to use the *Interwoven* standard image and link buttons (I'm assuming that you can now browse the workarea with these pugins).

Now here's the bit that confused the **** out of me for while. The iwlink and iwimg plugins override the standard and advanced versions that come with TinyMCE (I can understand why they did it as they can piggy-back on the existing event listeners).

We're fortunate in that links are just links in our content areas, we don't need to allow the user to do anything special with them. What we did have to do was hide the target options, but that was easy enough using style="display: none" in the pop-up HTML (the same applied to all those scary table and table cell options like "background image"!! What the...?)

Images are a little more problematic for us as they need to have classes for the correct styles to be applied (float left, float right, five standard sizes and custom size). When you need a fair bit of customisation, it's probably easier to start from scratch writing your own plugin and forget about the IWOV one.

I'm guessing that the insert image plugin I've written probably wouldn't fit your requirements, but I can post it if you think that deconstructing it could give you a jump start. Let me know.

JessicaD

Thanks for the offer (that's really nice of you), but after some research, the support rep found that iwBrowse in the code line you pulled is pointing to a custom file that isn't available ootb. The consultant we had been working with put that line in the config file, but the actual iwBrowse file was never installed on our server. We just need to develop our own browser callback and that should fix it. I may be able to find that code in one of the other plug-ins and re-use it.

JessicaD

Just heard from support - this is a bug. It turns out that the SitePublisher/LiveSite side of things can access the advimage and advlink browse buttons using the iwBrowse callback but the Forms Publisher side of things doesn't have the same customizations, so iwBrowse is missing. We have to use the ootb insert image and insert link buttons, but at least the issue was identified.