2 years ago, I set up provisioning of new sites with site design and it works fine.
Lately my implementation of PnP PowerShell
Invoke-PnPSiteDesign -Identity $siteDesign -WebUrl $preURL+$project -Connection $projConn
has conflict with the content type in the {tenant}.sharepoint.com/sites/contentTypeHub
How can I stop the usage of the content type gallery ?
Thanks
Related
In our SharePoint online site, we don't see the script editor web part from media and content section of webparts category. I have googled and found some relevant information like by default scripting will be disabled in SharePoint online... we need to enable it from SharePoint online admin center...as per the documentation,the changes may take 24 hours to get reflected - now it's been more than 24 hours but still we don't see the script editor web part from SharePoint online page. Any help will be much appreciated.
Thanks
Rahul
This is a known behavior in SharePoint online - sometimes even though we enable the custom scripting, we will not be able to add the script editor web part. For that we need to run the below powershell code:
$adminUserID="youradminaccount#< sprnd.onmicrosoft.com >"
$userCredential = Get-Credential -UserName $adminUserID -Message “Enter password”
Connect-SPOService -Url https://sprnd-admin.sharepoint.com/ -Credential $userCredential
Set-SPOsite "https://sprnd.sharepoint.com/sites/TestSite001" -DenyAddAndCustomizePages 0
Reference URL:
https://global-sharepoint.com/2019/08/24/how-to-enable-script-editor-web-part-in-sharepoint-online-site/
I deployed and activated the SharePoint Learning Kit (SLK) to my SharePoint 2013 Foundation according to this video. In the video there is a Web Part called "Assignment List Web Part". But I don't have this one in my Web Part Collection.
I have all SLK Features activated but the Web Part is still missing.
Is my solution corrupted or is SLK not capable with SharePoint 2013 Foundation?
You have to activate the WebPart on Site Collection level.
Select Site Actions | Site Settings to get to the site setting page.
Under Site Collection Administration select Site Collection Features.
Activate the feature.
This will add the "Assignment List Web Part" to the WebPart gallery.
http://blog.salamandersoft.co.uk/index.php/2010/07/sharepoint-learning-kit-1-5-features-you-can-activate/
For further questions regarding SLK, you might ask them on the Codeplex SLK Discussion Board.
There you have the chance to discuss your questions with other people facing the same problems and even the developer himself.
Here is my problem:
I have a US server with language pack installed.
I created a site collection in french.
I localized my feature that creates new content types.
If I activate my feature via the site collection (Web), my content types are in french.
If I activate my feature via PowerShell, my content types are in english.
I want to be able to activate my features via Powershell and have the right language used. Is it possible ?
Despite the examples I found on the Sharepoint server, it's not recommended to define displayname of fields in the content type itself... so got it working
When I create my feature I have the following choices for feature scope:
WEB
SITE
WEB APPLICATION
FARM
Which is the correct scope to select if you want your feature to be available in :
Site Settings > Site Features
Might seem trivial but its driving me up the wall, thanks....
That would be Web, using the SIte scope will make it available in the Site Collection features
I have some custom SharePoint site definitions that are deployed via SharePoint wsp solution packages. They appear to work fine. I can deploy them fine via the stsadm command line, and my C# code running in some features can also deploy sites based on them. My webtemp.*.xml files appear to be correctly placed in the 12\1033\XML folder when my solutions are deployed. My problem is that they just don't show up in the central admin app when I try to Create Site Collection. Why not? I don't even know where to look for this.
EDIT:
Hmmm.. About an hour later I happened to go back to the create site collection page and my templates were there. I'm not sure what was up... weird caching somewhere or something.
I also should have been more clear that these solution packages had been successfully deployed many times on my dev box, so I didn't expect there to be a problem (with the deployment aspect anyway) on this other server.
Many tasks in SharePoint are queued and then executed via timer job. An IISReset causes the web applicationt to be reloaded into memory and for configuration information for example the web.config to be reloaded.
To give SharePoint a "nudge" and cause jobs to execute you might try:
stsadm -o execadmsvcjobs
Do you have the publishing feature enabled? I read that content types can't be saved in templates, so they don't allow publishing sites to be made into templates. This is perhaps linked to why they won't show you the ones you already made.
Although I don't have access to a central admin to verify, this is the case from within my site collection.
Did you forget to run iisreset ?
This is needed for SharePoint to reload site templates.
If you use the Record Center as the template for your root website, templates (.stp files) in your template library will not show up when creating a new list.
There is some weird bug that makes this happen.
Here is code that you can try running in the SharePoint PowerShell. The return value for GetCustomListTemplates($web).Count will be zero if you have the root web made from the Record Center template.
$site = get-spsite("http://localhost")
$web = $site.RootWeb
$list = $web.Lists["TestDocLibrary"]
$list.SaveAsTemplate("MyListTemplate.stp", "MyListTemplate", "My List Template", $false)
$site.GetCustomListTemplates($web).Count
More information can be found at the following links:
http://social.msdn.microsoft.com/Forums/ar/sharepoint2010general/thread/c5455a27-360a-465c-91d5-f81beeac6789
http://sharepointrecordsmanagement.com/2011/02/