Tag Info

New answers tagged

1

What is going on is that Visual Studio deploys your solution globally and your feature is being activated on all webs. This is how it works. First of all set the project property of "Active Deployment" to "No Activation". Deploy the solution. Then activate/reactivate the feature on a specific web. The C# code, though, will be deployed to GAC or WebApp and ...


1

Either will work - the feature ID or the feature name. From Technet documentation here: https://technet.microsoft.com/en-us/library/ff607803.aspx Specifies the name of the Feature or GUID to uninstall. The type must be the name of the Feature folder located in the 14\Template\Features folder or GUID, in the form 21d186e1-7036-4092-a825-0eb6709e9281.


0

The Enable-SPFeature cmdlet enables an installed feature at the given scope. If the feature is a farm feature, no URL is needed. Otherwise, provide the URL where the feature is to be enabled and it will be enabled at the proper scope based on the Feature definition. The Identity is a requied field. It is the name of the feature. For more info check


3

You might be using a wrong 'Web' object. It shouldn't be System.Web or Microsoft.Web. It should be from Microsoft.SharePoint.SPWeb namespace. So first of all you need to get an 'SPWeb' object from 'properties'. Depending on where you are activating the feature, it should be something like this: If you are activating a Web scoped feature: SPWeb web = ...


1

There is no declarative way to make the page deployed through File element to show up in the Quick Launch. Check the attributes of File Element here: https://msdn.microsoft.com/en-us/library/office/ms459213.aspx So, using the event receiver may be a right approach.


1

Add this code to your FeatureActivated method of the Event Receiver: public override void FeatureActivated(SPFeatureReceiverProperties properties) { using (SPWeb web = (properties.Feature.Parent as SPWeb)) { web.AllowUnsafeUpdates = true; string headingTitle = "myNavigation"; // Navigation Title ...


1

Their is no OOTB way to convert the Public site into team site as both using the different template. Now two things you can do. Create a team site and move all the content manually Use the 3rd party tool to convert it. you can try Sharegate, Metalogix.


2

I found the solution. Forgot to publish the content type and run the timer job (content type hub & subscriber). After that everything worked! I don't have to run the timerjobs in the feature (code), it works without it!


0

This might also help someone: Get-SPSite -Limit All| Where-Object {(Get-SPFeature "PublishingSite" -ErrorAction SilentlyContinue -Site $_.Url) -ne $null } | Select Url Taken from this blog post. See full reference: https://technet.microsoft.com/en-us/library/ff607945.aspx


0

I think you have to recreate the complete template again or may be try to use 3rd party tool if they able to migrate it. also check the below codeplex solution, i am sure will help you. Migrating the SharePoint 2007 “FAB 40” templates to SharePoint 2010



Top 50 recent answers are included