Posts Tagged ‘sharepoint’

Annoying “This page contains both secure and nonsecure items” warning and how to get rid off it?

January 20, 2011 Leave a comment


Just a quick and short post about this warning and what are possible solutions to get rid of it. So the warning happens sometimes when you setup SSL for example on Windows Sharepoint Services (WSS) site. After that, anytime you open the site,  or navigate back and forth this warning pop-out.


This happens because some of links on your site point to http instead to https. So if you have some links, pictures or something else that is having http in link you have that warning. Also, what I personally experienced is that this error happened because of using specific Windows Sharepoint Services theme (Basic theme).

How to solve the problem?

Change Sharepoint theme. Go to Site actions> Site settings > Look and feel > Site theme  and change theme to default.

Check if anything (links, pics…) on your site is still using http links. Change those to https or start using relative path instead of absolute. Absolute link is –>  and relative (in Sharepoint)  is –> _layouts/images/  or //

Change browser settings:

          1. Tools > Internet options
          2. Security tab > Custom level
          3. Scroll down to “Display mixed content” and select Enable
          4. Click Yes on  Security warning pop-up
              Hope that solves your problem.
    Categories: Misc Tags: , , , ,

    Opening Infopath forms from Sharepoint site with virtualized Infopath

    September 12, 2009 1 comment

    Opening documents from Sharepoint site with virtualized Office can cause problems.Today many companies implemented some version of Sharepoint as their internal document management system and overall document repository system. Sharepoint is great and easy to use, and companies can really benefit of Sharepoint’s use, so in some point they decided to use sharepoint site for various kind of documents. That’s really great, and everything work fine for those kind of documents if users have Office installed locally. They simply open Internet explorer, type sharepoint url and click on document they need. Of course, because everything is installed localy, when user click on, for example, xml document it is automaticly opened with Microsoft Office Infopath. Same rule applies to Word documents. But what when users are using virtualized version of Office applications? Well then the thing get little more complicated. When Office is virtualized with Microsoft Application Virtualization and then streamed to a client, every file association is discovered properly, so with virtualized Word, users normaly open .doc or .docx documents if these documents are placed somewhere on users disk. But if those documents are placed on Sharepoint site, then when user click on xml or .docx document,  SharePoint is looking for ProgID’s “Sharepoint.OpenDocuments.*” which are not part of file association, but are part of SharePoint COM objects. So when you try to open those documents with virtualized Infopath or Word you will get error that you don’t have appropriate application for opening documents, or something similar. But luckily things can be fixed.

    How can this be fixed?

    So if you have Sharepoint site and virtualized Office(Infopath or Word), you should do the following:

    1. Sequence Infopath (Word) by best practices, but then in shortcut phase of sequencing include shortcut to Internet Explorer (It is easy, on application phase just click Add new application and then browse to executable of local Internet Explorer.)
    2. Install Sharepoint services support from the Office CD. You can find this by normally installing Office and then in Office Tools subtree only check on Sharepoint services support.

    If you do all that, opening document from sharepoint site should normally work.