Web-Based Org. Charts do not generate correctly after switch from Visio 2007 to Visio 2010

After doing a bit of testing, it turns out that there's a fairly simple solution -- install Silverlight.

I know that Silverlight is required if you choose Visio 2010's default web page output format of XAML. However, my understanding had been that Silverlight wasn't required for VML output.

Regardless, the issue you've described is reproducible without Silverlight but doesn't occur after installing Silverlight. This may also explain why the web page output functions work correctly on some users' machines but not others.

BTW, I tested with IE8 but didn't test with IE9.

Let me know if this solves the problem. In the meantime, I'm going to pose this question to the Visio development team because I'm curious!

That was my understanding as well for VML; it didn't do this in Visio 2007; also problem is that administrative rights prevent end-users from installing Silverlight (I know because I originally published in XAML).

How long do you think it will take the Visio Dev. Team to get back to you?

Can't predict how long before I will get an answer... but stay tuned...

The few lines of code don't happen to be in the "widgets.htm" document do they?
I already use a custom bit of code in there to create a printable version of the charts (linking to a pdf) so it wouldn't be that impactical if it was the same document that was tweaked.....

No -- it's in the frameset.js file. Below is the response from Visio MVP John Goldsmith in case you want to fiddle with his suggestion. I've haven't tested it but from his description, I suspect it fixes the hyperlink issue but probably doesn't change the search failure.

=  =  =  =  =  =  =  =  =  =  =  =  =  =
I notice that OnShapeClick (in frameset.js) is only testing for isUpLevel, which currently only returns that silverlight is supported and enabled.  With SL disabled, isUpLevel returns false and so nothing else happens in the function.  You can actually set it to true in the console and then it functions correctly and you navigate off the right place.

I can’t remember whether isUpLevel used to include vml, I think possibly it did…..ok, looking at an old frameset.js file I see the following

var isUpLevel = (MSIE && ver >= 5 && !isMac);

but now it’s :-

var isUpLevel = slSupported && slInstalled;

I would guess that you’d have to edit frameset.js and include an OR in the OnShapeClick so that it becomes the following:

function OnShapeClick (pageID, shapeID, jsEvent, slEvent)          // slEvent - Required for Silverlight only
{
                if (isUpLevel || vmlSupported)

I’m guessing also that the slEvent comment isn’t correct?

…just tested the above and that works.  Can’t vouch for side effects...
=  =  =  =  =  =  =  =  =  =  =  =  =  =

Just responding so that I can ask another question; let me know if the Visio Dev team gets back to you and hopefully releases a patch.

Don't suppose this ever went anwhere; I'm about ready to downgrade back to 2007 unless there is a patch I'm not aware of?

Apologies that I dropped the ball after asking the Visio team for assistance. I'll ping them again right now....

Should I be going somewhere else to submit a Hotfix other than here:
http://support.microsoft.com/select/Default.aspx?target=assistance

When I put in my PID number it says "The product ID number you entered is not supported in the country that you have selected. Enter another product ID number or select a different support option below."

(I never selected a country)

Thanks.

That is the right place as far as I know. When I followed that link, it took me to a page that asked for country. Perhaps you've been there before and answered the country question a long time ago?

As to why it doesn't think Visio is a valid product, I don't know. You might try coming in from a different angle... e.g., on this page
   http://support.microsoft.com/contactus/
when I clicked "Contact Microsoft Technical Support" in the email section, it asked me the country question again.

BTW, you should be able to save yourself some time if you tell them (whoever "them" ends up being!) that a program manager on the Visio team has already confirmed that this is a bug. While I'm not at liberty to reveal his name in a public forum, they are welcome to contact me, Scott Helmers, Visio MVP, scott-EE at taskmap.com, for corroboration.

Will follow-up on the question once Microsoft has provided a hotfix/response