It is strongly advised against modifying the corev4.css file.
This main reasons being that as soon as you apply the next update, your css customisations will be lost as the file will be overwritten, and your changes affect the entire farm.
It's recommended that you create a new CSS file, store it either in a folder in LAYOUTS in the SharePointRoot folder ...
You can create a theme very easily by using Microsoft Theme Builder. But to do a complete look and feel you are going to have to look at time vs effort vs effectiveness. Branding SP 2010 is very feasible.
If your site is a company Intranet, try using a custom theme and then adding a picture banner, this is minimal work and can make a site look very nice. ...
First you need to understand themes in 2013.
Start here for the basics
Then here to grasp how to make a custom one
Then you need to understand where and how they are set from this, then you can alter it., something like this:
ThmxTheme oTheme = ThmxTheme.Open(siteCollection,"_catalogs/theme/themename.thmx");
I achieved this goal by adding the following to my App.js:
//Build absolute path to the layouts root with the spHostUrl
var layoutsRoot = strHostUrl + '/_layouts/15/';
//Create a Link element for the defaultcss.ashx resource
var linkElement = document.createElement('link');
I hope OP meant following thing from site settings.
To check whether this option is checked or not, we need to make a REST call to the following end-point
It will return all properties under the web. Now find the property named OData__x005f__x005f_InheritsThemedCssFolderUrl. If it's value is "True", then the theme is being ...
You could have a feature which programmatically applies your custom theme, and staple this feature to the site definition at the site collection level.
This means that every subsite that's created from the site definition within your site collection will automatically activate the feature and run your code to apply the theme.
Some links to help:
You can change the "Look and Feel" for My Site using the URL:
Its the same URL as defined in "Change the look" section of Site Settings.
There are two possibilities to get the ThemedImageUrl of the spcommon.png File. You can use C# Code and the Method GetThemedImageUrl() which was allready mentioned.
But SharePoint 2013 also provides a new Control called ThemedForegroundImage. Take a look how to use it:
<SharePoint:ThemedForegroundImage ThemeKey="spcommon" ImageUrl="/_layouts/15/images/...
In most cases, IsDlg=1 parameter should help you to display the page without chrome. This works for both application pages and site pages, and doesn't need any coding.
So, if you navigate to
, you will get it without any chrome.
I haven't worked in a lot of anon environments, and it was always my belief that themes were only available once authenticated. If you needed to style something to anon users, you'd need to use a custom master page and/or a custom CSS sheet.
When I started to brand http://pirateeric.sharepointspace.com, themes didn't show up when I wasn't logged in so I ...
In SharePoint 2013, a Composed Look is the combination of following::
Hence can easily be set via PowerShell
$themeName = "Sea Monster"
$SPSite = Get-SPSite "http://sp2013/"
foreach ($SPWeb in $SPSite.AllWebs)
$SPWeb.allowunsafeupdates = $true
$fontSchemeUrl = $SPWeb....
For Publishing Site or sites have publishing feature enabled, you can use the Design Manager as the following:
To inherit Master Page / Theme of the Main Site to the subsites.
Look and Feel > Design Manager > Publish and Apply Design.
For Site Master Page Check
Reset all subsites to inherit the Site Master Page Setting.
For System Master Page
I guess someone changed the color of the webpart in your stylesheet (or in a custom stylesheet) Or added style blocks in the masterpage, pagelayout, pages,...
If you use IE, press F12 to show the developer toolbar. When you select the arrow-button on the toolbar, you can click on the webpart and the toolbar will then show you what style's it contains. It's ...
It is completely possible to do on top of SharePoint Foundation - it supports all the normal themes and master pages and so one. It has it's limitations, being free that shouldn't be a surprise, for example if you going to have multiple sites and want to share common master pages it is a pain, where this is simplified in Standard and above.
If you going for ...
I think the theme gallery is one of the default libaries created from SPRequest/COM (I can't see it in the hive)
So you could use the same trick that site provisioning uses, wait looping until certain lists are available.
#create site collection
$filename = "c:\blah.thmx"
$bytes = [System.IO.File]::ReadAllBytes($filename);
$name = [System.IO.Path]::...
There are third party tools, like Axceler ControlPoint that give this type of functionality. Their methodology is to use event receivers to detect these types of changes and to block them. Being in an O365 environment, I'm not certain if you'd have the ability to create an event receiver or not (haven't used the cloud version ever).
Well, it will depend on a couple details.
If you're wanting to remove the permissions for all your users, you can do the following, via Central Administration.
Visit Central Administration > Application Management > Web Applications > Manage Web Applications.
Select the Web Application that you want to restrict the themes on.
Click on “Permission Policy ...
You can change the content of that zone through PowerShell, it's managed by the SuiteBarBrandingElementHtml property on the WebApplication object :
$app = Get-SPWebApplication -Identity "your-web-application-url"
$app.SuiteBarBrandingElementHtml = "<div class='ms-core-brandingText'>Your Company Name</div>"
Thanks to the other answers I have solved the problem.
The default css file is automatically linked when using the App, but using Keith Tuomi's code to define the css file is a good idea to ensure linkage.
I went through the css file and found the appropriate class called ms-ContentAccent1-bgColor which gives the color.
I am going to test if this works ...
Check the documentation your version of $SPWeb.ApplyTheme no longer works for SharePoint 2013
This is what I've got to work so far:
$file=$web.GetFile($web.ServerRelativeUrl + "/_catalogs/theme/15/palette005.spcolor")
Note everyone - SPWeb.ApplyTheme is not obsolete - only the method with the signature ApplyTheme(string) - that was for applying a theme by passing only the theme name. The method SPWeb.ApplyTheme(String, String, String, Boolean) is perfectly fine (see https://msdn.microsoft.com/EN-US/library/jj251358(v=office.15).aspx). That allows you to specify the URLs ...
document.getElementById('lblSomething').innerHTML = "Here is REALLY something!";
without error handling will most likely cause runtime issues because if the code runs before the label is rendered it will throw a global JS exception causing the issues I already mentioned.
Yes, you can deploy custom themes on a sub-site level.
Add your custom theme at a site collection level where the sub site exists from Site Settings > under Web Designer Galleries, select Themes. Click on the folder 15 and upload your Theme here. From here SharePoint takes over and creates a new set of icons based on your colors and make it available from ...
It's for SharePoint 2010
Please follow the below steps:
Go to root level
In Site Collection >> Site Actions >> Site Settings >> Site Collection Administration section >> Site collection features
There is one feature named SharePoint Server Publishing Infrastructure >> Click 'Activate' button
Then go to subsite
Site Actions >> Site Settings >> Look and ...
Here's a complete example I extracted from a working solution.
Add the .js and the .css to the .master
<!-- Must be located under Themable for the Theming Engine to work https://blogs.msdn.microsoft.com/sharepointdesigner/2010/04/09/working-with-the-sharepoint-theming-engine/ -->
Currently there's an issue with the site themes. Maybe your question has to do with this issue?
See this twitter converstation for more details. https://twitter.com/wictor/status/1034811057397751809
If this is the same issue, the workaround is:
Sorry everyone! We're aware of the issue and actively investigating. I
will note that as a workaround, if ...
The minimal.master in SharePoint 2010 is intended for a particular page (search pages I think). It is a slightly unfortunate name because we used to use that to describe master pages with minimal branding and chrome intended for normal pages. The term is now "Starter Master Page" and there are a few around for you to use.
The error is probably due to a ...
Here's how to do it:
Create a Module SPI
Set Url for the element to _catalogs/theme, List to 123 and RootWebOnly=true
Add the thmx file to the Module SPI and set the Type attribute on the element to GhostableInLibrary
Add it to a Site Collection scoped feature