7

On the site collection level, the SharePoint Publishing Infrastructure Feature needs to be active, and on the web level, SharePoint Server Publishing needs to be active. If not, you are not allowed to change master page.


6

To achieve that: Add an empty element item to your project. Then add the following code to the Elements.xml file. <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <CustomActionGroup Id="TestCustomGroupId" Location="Microsoft.SharePoint.SiteSettings" Title="Custom Site Settings Group" Sequence="100" Description="" ImageUrl="/_layouts/...


5

I guess you found "Something went wrong..." in creating the group. The whole point of Office 365 groups is that adding users to the group as members instantly give the access to the sites resources, including files in the document library. You don’t have to worry about manually assigning permissions to all those resources because adding members to the ...


5

I use that 'restricted interfaces for translation' when I have people who have contribute rights to a list in a site, but don't have any rights to the site itself. In 2010, giving a person contribute rights to a list, gave them 'limited access' to a site (SharePoint did that automatically). They had no trouble contributing to the list. In 2013, that same ...


4

I totally agree that this is inconsistent and a bit misleading. Assuming that tranforming the solution to the Sandbox is a none starter, a few thoughts... You could maybe re-scope the feature to the Web (I'm assuming that it is currently the scoped at the Site) and the just activate it on the root web. That would probably raise another issue though as I ...


4

Try using this code for adding custom action to the site settings page. // Add site settings link UserCustomAction siteSettingLink = clientContext.Web.UserCustomActions.Add(); siteSettingLink.Group = "SiteTasks"; siteSettingLink.Location = "Microsoft.SharePoint.SiteSettings"; siteSettingLink.Name = "Sample_CustomSiteSetting"; siteSettingLink.Sequence = 1000;...


4

try the below code and tweak it as per your requirement. $site=Get-SPSite "http://servername:1111/" $web=$site.RootWeb; $web.AllowAutomaticASPXPageIndexing=$true $web.ASPXPageIndexMode=[Microsoft.SharePoint.WebASPXPageIndexMode]::Never $web.NoCrawl=$false $web.Update() More detail at this site


4

It doesn't matter where you create them, groups only exist in one place, the site collection root. Creating them anywhere makes them available everywhere in the collection.


4

When you create a column name beginning with numbers in UI , SharePoint converts it internally as below: _x0032_ + Rest of the field name beginning with second digit. To answer your questions 1) Avoid column names beginning with numbers as general thumb rule/practice. If you must, then use Powershell to set internal name/display name. 2) Powershell/SSOM/...


4

Go to "Site Configuration" and then "Title, Description, and Logo" You can use this URL https://yoursharepointserver/yoursite/_layouts/15/prjsetng.aspx More info in this link Change the logo, title, and description of your team site. Note: you can change the URL if it is a subsite. To change URL of site collection, see that: best appraoch to modify a ...


3

As wjervis mentioned, Microsoft rolled out a feature in Office365 to limit the amount of scripting allowed in order to maintain the security and integrity of the sites in a tenancy. When the cutom scripting is disabled, parts or features that support scripting are no longer visible. Here is how to check: Log into Office 365 Click the Office 365 header ...


3

You can also use the SharePoint Color Palette Tool. It helps to build your custom colors or just make a copy and adjust one of SharePoint own palettes.


3

Because you have to use unique DisplayNames for Calculated Column Formulas (and internal Computed Columns you don't see those in the UI) So there is a check for Duplicate names in a lot of (UI) code You can change DisplayNames with code.. CSOM, JSOM, REST, whatever you prefer: My (private) CalcMaster tool does it (Column3 renamed to Column1) for ...


3

The whole set of codes is as follows- <script> $(document).ready(function () { SetAccordionQuicklaunch(); }); function SetAccordionQuicklaunch() { var caretMarkup = "<a href='#' class='accordionControl contracted'>&or;</a>"; // initialize $('#sideNavBox .root.static > li.static').each(function () { if ($(...


3

You can change the title of the site collections by going to site settings > Under Look and Feel click on Title, description, and logo. here you can update the Title of your Site collection. You cant change the URL of site collections once it created. there are couple of possibilities. If site is not big enough then save that as template include content ...


3

If you stop inheriting permissions, the users with access remain to have access. You need to remove the users that are copied over from the parent. Next to that option, some users have persmissions as a site collection admin, or on the web application level in Central Admin.


3

Starting from Sept 2018, this feature has been deprecated in SPO and replaced with new File move and copy functionality in the modern views Reference - SharePoint Site Content and Structure (In Office 365) Admin message center ID - MC143382


2

Well whatever was working in 2007 is still working in 2010 (and 2013). You need to make sure that you store the properties in the .AllProperties bag. The global steps are : Create an administration page and deploy it in the 14/_layouts/your-project/your-administration-page.aspx. Visual Studio 2010 (with CKS:DEV) or 2012 (with Visual Studio Tools for ...


2

Yes, you can do it. Use this: $("body #s4-topheader2. ul li ul li.static > a").each(function(index) { if(index!=2) { $(this).attr("href","javascript:void(0);"); } }); Cheers !


2

Basically to add some custom settings for a site you can use a SPWeb = SPSite.RootWeb ( property bag to store there settings (key, value). SPWeb.Properties Other way is that you can store some info in web.config, but i would not advise doing that. Other way as it was already said try using the custom list for properties. And the last check out the ...


2

The alerttemplates XML will have templates for several list types. You will find the structure of the templates enclosed in <AlertTemplate Type="List" Name="SPAlertTemplateType.GenericList"> and a similar tag for announcement list. However modifying the alertemplate XML directly is not recommended. Also, if you modify the XML, the template change ...


2

I received this error after running a patch (Dec 2016) on SharePoint. The thing that worked for me is running this in Powershell: Initialize-SPResourceSecurity (don't forget to run this first: Add-PSSnapin Microsoft.SharePoint.Powershell;) Credit: https://www.habaneroconsulting.com/insights/the-managed-metadata-service-or-connection-is-currently-not-...


2

OK, it turned out that the Managed Metadata Service was not associated with the web application hosting my site collection. So to fix that, I went to: Central Administration > Application Management > Configure service application associations Once there, I found my web application and then opened Application Proxy Group. It turned out that Managed ...


2

Yes, it'll be in the ULS, look for POST entries around "/_layouts/quiklnch.aspx" or just ask the Site Collection Administrators who did it :)


2

I encountered the same error a few days ago. Reported it to MS Support and they told me there might be a bug in SharepointOnline which causes the Managed Properties page to default to the incorrect level of site instead of sitecol So avoid using this URL _layouts/15/managedproperty.aspx?property=RefinableString00&level=site And simply use this URL ...


2

I think there is no straight answer. For common branding and site provisioning scenarios here is some info: Using Apps. If you look closely to Microsoft Office 365 Patters and Practices (o365 Pnp) guidance most of samples is demos or presentations is to use provider hosted apps. There you have your own pages with CSOM and you can do quite a lot (set master ...


2

I feel you, I had the same problem, therefore I only can tell you about my experience and you need to see whether it matches your problem. What I need to mention at the beginning is, that the visibility of those settings come with the "Permission Level" of a group. I have implemented a Document Library on a site, where users can post document sets and ...


2

You can do it through Welcome Page option but i guess for that you will need to activate Publishing feature at site level. The other options are If you want to set a Custom Page as a Home Page in a typical SharePoint Team site, you can simply do that by Opening the Page and selecting Page tab -> Make HomePage button to set this particular page as default ...


2

Site collection admin and farm admin are two different roles. Being a farm admin allows you to perform farm level operations such as working with service applicatons, managing web applications in the farm etc.. whereas the power of the site collection admins is only limited to that particular site collection. This design allows delegation of responsilbites ...


2

Back in SharePoint 2003, we had groups at both site collection (root) level and sub-site level. From 2007, this does not exist anymore (unless with a deprecated API). All groups are now site collection groups. This means a group created at a subsite-site level is actually a site collection group, i.e. it's created at the root level, without any notice! ...


Only top voted, non community-wiki answers of a minimum length are eligible