Hot answers tagged features
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".
4
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 ...
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 ...
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 ...
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
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
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.
...
1
Each custom form in lists actually contains a specific ListView web part, actually if you properly customize it, you have hidden most-likely the Default one, and added your own, for which you customize the behavior.
All this to say that actually you are dealing with provisioning of duplicate web parts, which Waldek has also explained here - ...
1
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())
{
...
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 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
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 ...
1
You have to use following command to enable the feature:
Enable-SPFeature FeatureFolderName -Url http://server/site/subsite
For upgrading FEATURE using powershell, see this excellent article: http://www.sharepointnutsandbolts.com/2010/08/feature-upgrade-part-5-using-powershell.html
1
You can force a removal of a feature using the -force flag in the stsadm deactivate command.
See the MSDN article on the feature:
http://technet.microsoft.com/en-us/library/cc262680(office.12).aspx
The web part may still appear in the web part gallery, you have to remove the reference manually after the feature has been removed.
1
The answer, like so many with SharePoint is it depends.
The only way to be sure, is to test it, it really depends on what is being done within those features that will determine what will happen. Even if the data remains, you might has issues with items that were tied to features that no longer exist.
If you need to ensure the data is kept back it up ...
Only top voted, non community-wiki answers of a minimum length are eligible
