Tag Info

Hot answers tagged

7

In order to view the Closed Web Parts, you just need to do: "Add Web Part" in any Web Part Zone Search for the "Closed Web Parts" category in the Web Part selection menu that appears on the Ribbon Your closed web parts should be right there


6

I've successfully done this in SP 2010 with PowerShell. I've done things slightly different, so let me try to translate and see if it works out for you. Adding a Web Part to a WebPartZone For your first section, add an .Update() on the page creation to commit the change to the DB: PublishingWeb pWeb = PublishingWeb.GetPublishingWeb(web); string pageName = ...


6

I think what the OP is after is a way to store information that can be made accessible globally. If it is indeed the case, then what can serve this need are property bags. Property bags are a place to store metadata or properties of your SharePoint sites. The Property Bags are implemented as a hash table consisting of property names and values; they can be ...


6

I don't know of a configuration setting that will turn off the Add button in the Calendar but you can hide it by placing a Content Editor web part on the page and adding the following CSS to the Content Editor. Be sure to click the Edit Source button in the ribbon and paste it in the HTML Source. <style type="text/css"> .ms-acal-rootdiv ...


6

Edit page Edit web part Appearance --> Advanced --> Title URL Remove value of field Save If that doesn't do it: place a "#" in the Title URL field If still that is not good enough: place "###" in the Title URL field and jQuery(document).ready(function () { $('a').filter("[href='###']").each(function () { ...


5

How to add WebPart client object on page via JSOM function addWebPart(webUrl, pageUrl,webPartXml,zoneId,zoneIndex, Success,Error){ var context = new SP.ClientContext(webUrl); var web = context.get_web(); var file = web.getFileByServerRelativeUrl(webUrl + pageUrl); var webPartMngr = ...


5

Here is a way to do it in sharepoint 2013 in visual studio 2012 1)Create a empty sharepoint 13 solution Farm solution . 2) Add a sharepoin 13 project into it . 3)Add a mapped foder "Resources" to the project . 4)Now you gonna add three resources one for english "testMutliLing.en-US.resx" and one for german "testMutliLing.de-DE.resx" and one default ...


5

You can add a simple label inside of your web part like: <asp:Label runat="server" ID="LabelWelcome"></asp:Label> And in the page load method in code behind set the text of that label like: this.LabelWelcome.Text = "Welcome " + SPContext.Current.Web.CurrentUser.Name; Then just set Chrome Type property to None in web part settings, so web part ...


5

Try to wrap it in {? } {?{searchTerms} (contentclass:STS_ListItem OR IsDocument:True)}


5

You cannot open that web part from "Web Part Maintenance Page" again. Instead you have to "Edit Page". Then click "Add web part". From left pane, in the categories click "Closed Web Parts", and then select your closed web part to be restored.


4

This code iterates all sub folder of your root folder and gets items by your query from subfolders foreach (SPFolder subFolder in docLibrary.RootFolder.SubFolders) { SPQuery oQuery = new SPQuery(); oQuery.Query = "Your Query" oQuery.Folder = subFolder; collListItems = oList.GetItems(oQuery); ...


4

The doctype of the default master pages isn't for HTML5 so I doubt it, you would need to set up a new master page (even a duplicate of the built in ones) with the correct doctype to use HTML5. You also have to then be wary of the CSS implementation as the master page normally forces IE10 compatibility but this could be resolved when you create your HTML5 ...


4

Click on Site Settings->Edit Page. Select the list on the page and click Edit Web Part. In the Appearance section, provide the Title and select chrome type to Default.


4

Don't worry. The pure use of CreateChildControls is only due to old habits of SharePoint developers due to the way Web Parts was developed in the past. If you prefer to build your web parts declaratively due to the increased productivity then just use that method. The only reason to prefer CreateChildControls is if you need the extra flexibility of adding ...


4

From a user perspective, there is no difference between web parts and app parts. Both add functionality to a SharePoint page. Technically web parts run inside a SharePoint context, and as a consequence may make an entire page unresponsive if the web part fail to load. An App part run outside SharePoint context and displays its result in an iFrame. If an app ...


4

Just hiding/removing +Add button, does not prevent the user from creating calendar Events using Calendar View, since the Events could be created by clicking inside calendar area. So, if you are interested not only in hiding/removing +Add button you could consider the following approach. How to disable the calendar events Example 1 ...


4

The SharePoint WebPart has its roots back from the 2003 version where it inherited directly from Control because ASP.NET had no concept of a web part and SharePoint as in many other cases implemented a lot of the functionallity which was moved into ASP.NET 2.0 in order to allow SharePoint to become a real ASP.NET application in 2007. After ASP.NET 2.0 ...


4

What you're asking is a bit complex to implement, but it's possible. You need to use AssetPickerDialog to get the same behavior as what you've mentioned, to pick up the image from library. I've implemented AssetPicker once, but that's for a different implementation, kind of searching entity from custom database. And that AssetPicker was triggered from a ...


4

You're missing the WebId property: var xlv = new XsltListViewWebPart(); using (var oSite = new SPSite(" http : / / app:3333/ ")) { using (var oWeb = oSite.OpenWeb("/ProxymIT/Direction")) { var oList = oWeb.Lists["AdministrativeNotes"]; //your list name xlv.WebId = oWeb.ID; xlv.ListId = oList.ID; xlv.ViewGuid = ...


4

Try using the same Google RSS feed URL without HTTPS, then it should work. so instead of https://news.google.com/news/feeds?cf=all&ned=in&hl=en&topic=n&output=rss use http://news.google.com/news/feeds?cf=all&ned=in&hl=en&topic=n&output=rss I did a quick test and it worked in SP when using the HTTP URL but not ...


3

It is strongly recommended not to create any custom web parts for a such cases. FAQ SharePoint List Create SharePoint List for storing FAQ entries (for example, rename the Title column to Question, add column of type Multi-Line Text and name it Answer) Display FAQ items Probably the simplest way for displaying FAQ items would be to modify the default ...


3

The configuration panel of the web part is called Tool Pane and you can open it using this simple JavaScript snippet : lblErrorMessage.Text = "<a href=\"javascript:MSOTlPn_ShowToolPane2Wrapper('Edit', this,'" + this.Parent.ID // Id of the current webpart + "')\">Edit Web Part</a>"; this.Parent.ID : return the WebPart ...


3

Can a single web part be a provider and consumer? Yes Can you do web part connections without postbacks? Sort of. You can use UpdatePanels to do partial page postbacks Can you chain web part connections? I don't think so. As far as I know there is no way to indicate the order in which connections should be processed. In the example you gave the web part ...


3

The options at your disposal depend on if you are running the Enterprise SKU or one of the supported O365 plans. Generally speaking - if you are using Page layouts you already have Publishing Features Enabled (however since we may also be talking about web part pages I'll cover both) You have the option to use the Design Manager functions for publishing ...


3

A simple discussion board may work for your needs. You can do a little bit of customization to one if you need additional information or filtering abilities... If you are doing canned answers, you could just use a list.


3

It doesn't seem possible to retrieve all the web part properties (like TypeName) via CSOM But it could be performed via WebPartPagesWebService SharePoint Web Service as demonstrated below: function getWebPartProperties(pageUrl,completeFn,errorFn) { var soapEnv = '<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ...


3

To get a WebPart you use the Limited Web Part Manager The SPWebPartManager manages all the Web Part controls, functionality, and events that occur on a webpage.. For example using (SPLimitedWebPartManager wpm = web.GetLimitedWebPartManager(this.Page.Request.Url.AbsolutePath, PersonalizationScope.Shared)) { foreach ...


3

Lots of good answers to this. Angular JS and Durandal JS are the most popular SPA frameworks. If you like Knockout take a look at Durandal JS, a simple SPA framework built using KnockoutJS for all the MVVM features. The SharePoint JS client object model will give you most of what you need with regards to SharePoint, but you can use Jquery to make most AJAX ...


3

Since .dwp web part file corresponds to SharePoint-based web parts and .webpart to ASP.NET web parts, web part file can not be converted without rebuilding web parts itself. The difference between SharePoint-based and ASP.NET web parts The set of features provided exclusively by Microsoft.SharePoint.WebPartPages.WebPart is as follows: ...


3

It's an easy fix, at least this worked for me. Steps: Double click package in Visual Studio Go to Advanced tab Change the product version to 14.0 and you are good to go



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