-chris

Exactly which function is showing up as broken in IE?

Is this problem specific to IE, or is it a problem in the other browsers as well?

Are all users seeing this issue, or is it specific to you? There is a known issue with the Real Player Plugin and Flash that causes problems.

thanks

-chris

I did some digging and found that this file is referenced in the page source that opens when the "edit diagram" -button is pressed:

<script language="JavaScript1.2" src="/download/resources/com.gliffy.integration.confluence:gliffy-macro-key/resources/gliffy.js"></script>

Don't know if this is why the gliffy flash program doesn't open, but I thought it was worth to mention it.

Oh, and yes "all" users are seeing this issue. (At least the four guys I asked to test this)

var saveWarning = "false";

function checkSaveWarning(ev) {
//    alert("check save warning, ev: " + ev + " saveWarning: " + saveWarning);
	if (saveWarning == "true") {
		var warningStr = "We have detected that you have not saved your work in Gliffy.";
		ev.returnValue = warningStr;
	}
}

function setSaveWarning(b) {
    //this MUST be the first line.  Otherwise, Firefox seems to delay execution
    saveWarning = b;		
    //alert('setSaveWarning:' + b ); 
    //#alert('actual saveWarning is:' + saveWarning

This is what is inside the gliffy.js file. As you can see, the last function is missing a "}"

It looks like your gliffy.js is incomplete. For some reason, you're not getting the entire file.

Take a look at our wiki, where you'll see that gliffy.js contains a lot more content:

http://wiki.gliffy.com/download/resources/com.gliffy.integration.confluence:gliffy-macro-key/resources/gliffy.js

I'm not sure why you're getting an incomplete file. First, try re-downloading and re-installing Gliffy to see if that helps. If you still see the same problem, please take a look in your error logs and see if there are any clues in there.

Here is the Confluence documentation for locating your log files:

http://confluence.atlassian.com/display/DOC/Working+with+Confluence+Logs

Please let me know how that goes.

regards,

-chris

I tried to clear all private data from firefox, but even that didn't help.

I will go through the logs next if I can find something more useful.

Any tips on what to look for in the log files?

If you're seeing this problem on our wiki also, then it seems likely that there is an issue in your browser.

Can you please list the plugins that you have installed in your web browser?

thanks

-chris

• Adobe Acrobat, Adobe PDF Plug-In For Firefox and Netscape
• Java(TM) Platform SE 6 U13, Java(TM) Platform SE binary
• Java(TM) Platform SE 6 U13, Java Plug-in 1.6.0._13 for Netscape Navigator (DLL Helper)
• Microsoft Windows Media Player Firefox Plugin, np-mswmp
• Mozilla Default Plug-in, Default Plug-in
• Shockwave Flash, Shockwave Flash 10.0 r22
• Silverlight Plug-In, 2.0.040115.0
• Windows Presentation Foundation, Windows Presentation Foundation (WPF) plug-in for Mozilla browsers

I also just installed Google Chrome ( first time install to this computer) and it shows the same problem on our wiki and also on yours. The problem being that the gliffy.js file isn't loading fully.

I have now tested this on 4 separate computers and with firefox,IE,Opera and Chrome ( not on all of those 4 computers).
I'm just installing vista to a new laptop for a separate thing and I could test your wiki (with address http://wiki.gliffy.com/download/resources/com.gliffy.integration.confluence:gliffy-macro-key/resources/gliffy.js) on a clean install. I have a hunch it won't work on that either.

Are you sure you are not getting your copy of gliffy.js from a cache or something?

I'll report back when I have the fresh copy of vista installed.

Do let me know what you find out!

-chris

First tried to boot our firewall, but that didn't empty the cache. Finally we made a rule to the firewall so that our intra confluence pages don't go through the cache and now it is working again. Just a quick fix, because we are switching to new firewall boxes in a couple of weeks so it would be a waste of time to try to figure out how to empty the firewalls cache fully.

You can now close this "bug" as it seems that the only problem was our firewalls cache.

ps. Hope this helps in the future if someone runs in to similar problems

-chris