Tag Info

Hot answers tagged

5

I think any release date you see at present will be speculation as there is nothing official from Microsoft. Many have speculated that MS will try to align the Office 15 release date with their conference in November, so I suppose the best answer anyone can give you right now is "probably the end of this year".


5

It seems that not all features are active on the root site of your site collection. Some of the list templates, including the Communications list templates, are only available if a specific feature is activated. Please check the Site Features of your root site. You can do this by going to the Site Settings page, and then navigate to Site Features. Please ...


4

You should enable the "SharePoint Server Enterprise Site Collection features" at the site collection level. You can find the "Site collection feature" management link on the Site Actions>Site Settings page under the section "Site Collection Administration".


4

You can only have Content types at Site or List level. So, even if your feature is scoped as web the Content types will be added to the Site level (at root web). From there on, content type will be available, to be added to the lists and document libraries in all webs and so on.


3

The only 'fixed' information we know about dates at this point (early March) is that there will be a beta version of Office 15 and its companion software (SharePoint 15, Lync 15, etc) 'this summer'. We do not know anything beyond that, if 'knowing' is defined as what Microsoft has published. 'This summer' can technically mean anything up to and including ...


3

List template gallery (the url atribute of _catalogs/lt) is only available in the root web of the site collection. So you get an exception when the feature is activated in the subsite because it cannot find the specified list (http://sitename/subsitename/_catalogs/lt). The templates should be available across the site collection. Change the feature scope to ...


2

You can use delegate controls, check this article.


2

SharePoint 2013 reached RTM on October 11, 2012. Reference: SP Team Blog & Office Blog


2

Looks like there is something wrong with your site's Team Collaboration Feature (Site Actions > Site Settings > Modify All Site Settings > Site Features > Team Collaboration Feature). This adds a few list templates to the new list screen. Try deactivating a reactivating this feature. If that doesn't work, maybe its some permissions issues.


2

The entire WSP file is stored in the configuration database so you can always get it from there with PowerShell like: (Get-SPFarm).Solutions | ForEach-Object{$var = (Get-Location).Path + "\" + $_.Name; $_.SolutionFile.SaveAs($var)} When a farm solution is deployed the assemblies are copied to GAC or webapp bin folder. All the feature files are copied to ...


2

If you're working with Visual Studio 2010 make sure that new/old Feature is added in Package. You can use the Package Designer to create and customize a package (.wsp). For example, you can add SharePoint project items and Features, specify if the Web server is reset when the solution is deployed, and set the deployment server type. ...


2

To remove the link break the connection to the Search Center Step by step: Select Site Actions | Site Settings In Site Collection Administration click Search Settings In Site Collection Search Center select Do not use custom scopes. ... OK


2

You can try something like this in powershell. $allSiteFeatures = Get-SPFeature | Where-Object { $_.Scope -eq "Site" } $activeFeatures = Get-SPFeature -Site "http://sitecollectionUrl" $allSiteFeatures | ForEach-Object { $active = $false foreach($feature in $activeFeatures) { if($feature.Id.ToString() -eq $_.Id.ToString()) { ...


2

You cannot define feature dependencies cross scoped according to Activation Dependencies and Scope. In theory you can change the visibility once the site collection feature was enabled but you need to do the same for ever sub site that will be created. From my point of view the best way would be if you check in a feature event receiver of the web scoped ...


2

lets explain what you did! you had a feature that was built within a wsp, you deployed the wsp to a webapp and then activated the feature... you then decide to remove the wsp but forgot to deactivate the feature leaving you in the position that your currently in! next time deactivate the feature before removing the wsp, once you remove the wsp it removes ...


2

How to exclude Document Sets from List View using filters Assume we have OOTB Document Set content type (0x0120D520) added in Documents Library, then the following filter could be specified: Content Type is not equal to Document Set


2

as far as I know retracting solutions doesn't deactivate their features, so although you wont be able to find or activate/deactivate those features, their references are still there. on the particular case of event receivers, it could turn out to be a major problem. the receiver may still be attached and if you redeploy/reactivate you may end up with firing ...


1

Yup in your element.xml file you can add following tag, <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <WebTemplate Name="SimpleSite" Title="Simple site" BaseTemplateID="1" BaseTemplateName="STS" BaseConfigurationID="0" DisplayCategory="Simple sites" /> </Elements> Your project structure should look something like this, ...


1

This looks like a context issue, but I'm not 100% The powershell context issue in a nutshell: Powershell runs in a caches context, after installing or uninstalling a component you always need to restart the powershell command window to reload the owsvrdll and any custom DLLs. The different you are seeing is most likely caused by you sometimes closing and ...


1

This is the powershell script Initializing variables Write-Output "Initializing Varialbes" $SiteCollection = "site url" $FormName = "published xsn file name" $FormPath = "xsn path" Desabling Form Template Write-Output "Desabling Form Template" Disable-SPInfoPathFormTemplate -Identity $FormName -Site $SiteCollection Unistalling Form template ...


1

I think that you can use script from this post to retrieve list of all installed features on a farm, after this you can check this list and find out does your feature is included in this list or not.


1

This is how I would do it: Create a blank solution (sln). Create a SharePoint project to hold the Web Parts (this will also be one single WSP). Use Add Existing Project... to add the Web Part projects to your solution (sln). In your new SharePoint project create a Feature. Add the Web Parts to the new Feature. Now you will have a completely separate ...


1

Correct, you shouldn't modify SharePoint files in the _layouts folder. In your master page, you could add some CSS that targets that link and hides. Use a web inspector (like the IE Developer Toolbar) to identify the CSS class or ID that you could target to hide that link.


1

Simillarly as with Content Query Web Part (CQWP) also the Summary Link Web Part is governed by an XSL file in charge of rendering content available at the Site Collection Level in the Style Library called SummaryLinkMain.xsl. I would strongly recomand simply copy that file, rename it to your liking and then export your SLWP and change its attributes to ...


1

try this if it helps public static SPFile FindFileWithDocumentID(string docID) { SPFile file = null; string url = string.Empty; using (SPSite site = new SPSite("http://basesmc2008")) { string[] urls = Microsoft.Office.DocumentManagement.DocIdLookup.DoSearch(site, docID); if (urls != null && urls.Length ...


1

It appears that you don't have enough permissions to activate custom features. I would recommend you opening SharePoint Management Shell (run it as an administrator) and run the following powershell to activate features: Get-SPWebApplication nameofwebapplication| Get-SPSite -Limit ALL | % {Enable-SPFeature "nameoffeature" -Url $_.Url} One more thing you ...


1

You can easily have multiple features in a single solution, and each of those features can have different scopes (ie: web application and site collection features in the same solution). You do need to ensure that if they have dependencies on one another, those dependencies are setup. Are you "upgrading" the solution, or retracting and redeploying now that ...


1

Features do not have a possible scope of 'List' so the specifics of how each feature affects lists is wholly dependent on what artifacts the feature itself adds. As such, there is no way to look for lists affected by a particular feature. Instead, you will need to know what it is specifically that is blocking the upgrade. If it is an outdated ...


1

Phil Childs has a some PowerShell scripts that can be helpful (some tweaking may be required in your case) - Removing features from a content database in SharePoint 2010 using PowerShell (use the -ReportOnly switch to list out the Features) Bulk deactivate feature and remove farm solution in PowerShell There are two other tools from CodePlex that can ...



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