InfoPath Dev

   If this image doesn't show, a copy is attached.

I'm not familiar with what you mean by a published team site. Your screen shot does not display. It may be that you don't have adequate permissions to save a site as a template.

 I see your snapshot and raise you one...I'm pretty sure the site is team site, that's been published.  This is what mine reads. No 'save site as template', option.  

Here's a screenshot of the Site Actions > Save site as template from the Site Settings page of a team site, in case that helps.

So your site is a publishing site, not a team site?

 I just found the following; does it mean, that because I've already published my site, that I cannot save it as a template (the below references 2013, my site is in 2010)?   In previous versions you could still save a site as a template when Publishing is turned on by doing it manually.  In 2013 Microsoft closed that ...

 I tried the following instructions, but could not find an option to save site as template. Is it possible this feature has not been activated, and if so can it be - by me?On the Site Actions menu , click Site Settings.Note: On a site for which the Site Actions menu is customized, point to Site Settings, and then click the settings ...

 So - to answer how to get the XSL - if you save the form as source files, you'll see the XSL in the files. However, what I did recently to get checkboxes and option buttons to display properly in my print view was I used chars from one of the Wingdings fonts with conditional formatting to show / hide based on what was ...

 Check your SharePoint ULS logs - I'm guessing they will have more info on why this connection is failing in the browser. If you don't have access, contact your SharePoint admin for help.

 Hey, Rob - are there any conditions on your form load rule? Perhaps for some reason those are being evaluated differently in the browser. Another thing you could try while troubleshooting is to put the rule(s) that are on form load on a button in the form, see if you have different behavior when you click the button vs. form load.... ...