Tag Info

Hot answers tagged

2

I don't think this can be done using OOTB SP. At least without using JQuery or SPD


2

What you are seeing are references in your database after a solution/webpart that was not removed correctly. I assume that you just uninstalled and removed the solution? If you know in which site och sub site the web part and feature was activated, you could add and install the solution again to your farm and follow those steps: Go to the site or sub ...


2

there are couple of ways to remove it. Using the powershell script, check this link CodePlex solution SharePoint Feature Administration and Clean Up Tool


2

If you wanna display the latest items, i think you mean the Content Search Web Part. For this you need the enterprise license as it is not available to the foundation nor the standard edition. If you have a Enterprise license, add it by activating the Search-Driven content feature. SharePoint 2013 feature comparison chart all editions For the Search ...


1

contentclass:”STS_Site” contentclass:”STS_Web” This search query will return you all the site collections and subsites that the user has access to.


1

Create an External list and add a list view webpart. You will have the SharePoint user experience. You can use SharePoint Designer as well as Visual Studio for this. This is how to do using Visual Studio: Create SharePoint 2013 External List using Visual Studio 2012 Create an External List Using C# Modifying BDC Model Entity in Business Connectivity ...


1

looking at the web.config is not enough! check to make sure your dll is in GAC and that the assembly is correct. C:\Windows\Microsoft.NET\assembly\GAC_MSIL\ make sure your version and public key token are correct! you can check up against your dev enviroment, compare the two safecontrols.


1

According to this article Sandboxed Solutions support both custom actions as well as visual web parts. The following are not supported. Application Pages Custom Action Group Farm-scoped features HideCustomAction element Web Application-scoped features Workflows with code


1

It would throw errors at you if the web part is not deployed as a feature on the destination server. You need to package the web part via the Publish option, then use powershell to deploy the feature on the destination server and any errors present will no longer appear.


1

The preferred approach would be to change them in the Page Layout, create a new solution package and deploy that to the farm. This avoids unghosting of the page layout file. Or if you are clear about the consequences of unghosting you can go to the Master Page Gallery (http://sitecollectionroot/_catalogs/masterpage) and edit the Page Layout with SharePoint ...


1

Get the file attribute from the page and then get the LimitedWebPartManager. You add the webpart definition to the page. You can donwload it from the web part gallery but incase of a listview webpart I think you need to generate the correct xml yourself due to the references to lists, views, fields, etc.... public Guid AddWebPartToPage( ClientContext ctx, ...



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