Theme Installation: Pre-requisites

To ensure installation runs smoothly, there are a few requirements to be met before starting the installion procedure.

Publishing Features and Minimal Download Strategy
Office365 SP2013

SharePoint 2013 Minimal Download Strategy is enabled by default on Team and Community sites. To install BindTuning themes in one of these sites you need to deactivate the Minimal Download Strategy feature.

  1. On the ribbon click Settings
  2. Click Site Settings
  3. Under Site Collection Administration click Site Collection Features
  4. Activate the SharePoint Server Publishing Infrastructure feature
  5. On the ribbon click Settings
  6. Click Site Settings
  7. Under Site Actions click Manage Site Features
  8. Deactivate the Minimal Download Strategy
  9. Activate the SharePoint Server Publishing feature
Note: If you are working in SPFoundation, and don't have access to the Publishing Infrastructure Feature, you can go to the site features of each of your websites, and activate the theme features there.
Heads-up: Server Publishing Feature activation must be done in all sites where the theme is to be installed.

Enabling PowerShell Scripts
SP2013 SP2010

Note: This section is valid for Farm Solutions Only.

If runnning PowerShell scripts is not enabled, you may get errors like:

File C:\Scripts\Install.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.

File C:\Scripts\Install.ps1 cannot be loaded. The file C:\Scripts\Install.ps1 is not digitally signed. The script will not execute on the system. Please see "get-help about_signing" for more details.

To enable PowerShell scripts, proceed as follows:

  1. Run SharePoint PowerShell command-line with admin privileges
  2. Run Get-ExecutionPolicy to find the current policy
  3. Run Set-ExecutionPolicy Unrestricted to enable the system to run scripts
  4. Your system now meets the requirements to correctly run the PowerShell scripts
  5. Optionally run Set-ExecutionPolicy [oldpolicy], where [oldpolicy] should be the one found before in "Get-ExecutionPolicy", in order to get things back to where they were. This should be done after the setup is complete.

At the end of this procedure, if you still receive an "Access Denied" message, try opening cmd.exe (windows command line) by right-clicking and choosing "Run as Administrator".

Then execute the script again using the command line.

Have more questions? Submit a request


Got a question?

If you can't find the answer to your question, you can contact us.
We are here and happy to help.

Powered by Zendesk