Hot answers tagged

13

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.


8

saving session state varibles can be done using: public string Name { get { return Page.Session["SaveName"] as string; } set { Page.Session["SaveName"] = value; } } this is a getter/setter to save/get from session state to use this do the following: this gets the value ...


7

Web Part Pages are advantageous when you want to display information within your site in a different manner. They can be viewed very similarly to sub-sites because you can add them as links to your quick launch just like sub-sites however, they do not require you to create an entirely new site (which could contain new security groups, possibly pre-created ...


7

There can be many advantages if you target your users to the Web Part Page on which you have a view of a List. And they are as follows. The independent Web Part Page can be branded and have a more appealing look Instead of showing all of the items, Views are very useful in listing the filtered data. Which makes sense when you want your users to see only ...


6

You can use a "Wiki Library" that houses wiki pages - in this library's settings, there is a field called "wiki content" by which you can display the content without all the surrounding navigation. Try the following: Add the Wiki Web Part associated with your Wiki library, then Configure it to only display "Wiki content" and filtered for the name of the ...


6

Have you tried if (!Page.IsPostBack) { your code here } ?


4

A very odd question :) For me, comparing SPWeb (subsite) to page, is like comparing book to bookshelf. Yes, you can perform same operations with a site, but web part page is just a little possible part of the site. Actually, site can contain hundreds of web part pages, but with the same success it can contain none of them. Site is just a "box", a container, ...


4

Here is LINQ code that finds a Web Part with a title: string _webPartTitle = "mywebpart"; //Retrive the webpart with some title IList<Microsoft.SharePoint.WebPartPages.WebPart> _listFormWebParts = (from _wp in manager.WebParts.Cast<Microsoft.SharePoint.WebPartPages.WebPart>() ...


4

To brief it is actually a good practice to refer on a different page with list view web part added onto it. Reason is you can configure the new page such that user will not be able to use ribbon options (if want to restrict from navigating through list settings) Step to hide ribbon: Edit your webpart Select Toolbar Type to None Chrome Type to Border Only ...


3

A web part page with a list web part on it is actually exactly the same as "the list itself". When you say "the list itself", THAT is a web part page with a list view web part on it. Nothing more. So if you want to direct your users to a list called "My List", you can direct them to the default AllItems.aspx page for the list, or you can direct them to a ...


3

Adding a page in a page might be possible with using a page viewer webpart. Although I'm pretty sure that's not something you want to do. You might just want to add the webparts on the wiki page, which is perfectly possible.


3

You have two ways: Use the GetLimitedWebPartManager that give to you access on what web part you have on the current page. You can use JQuery to find all the div tag that using one of the following css class: ms-WPBody, also ms-webpart-, and also the webpart's id start with a "WebPartWP" Do some crawling on your DOM and you will find what do you need. ...


3

Web Part pages belong to a site. On a page, you can display and combine views from different lists or libraries that exist in the site. SharePoint offers a variety of options to sort, filter, connect views. If you add a new sub-site, the SharePoint interface doesn't allow you to display in the sub-site content that belongs to the parent site. I use Web ...


3

You can define the parameters normally in report builder but when you pass the parameters from query string you need to append it with rp: http://sitename.com/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/Reports/MyReport.rdl&rv:ParamMode=Hidden&rp:city=Perth where Relative report url is the url to your .rdl file (Report file) ...


2

This can be accomplished by the Out Of The Box feature within SharePoint 2007. As @Perplexed has mentioned, you need to have publishing feature enabled in your particular site and site collection to achieve this. Follow the steps - Site Actions -> Site settings -> Site Collection Features -> Activate SharePoint Publishing feature Go to the particular ...


2

What are you looking for is what is know a Page Layout (a simple .aspx page created usually via SharePoint Designer direclty on the Top-Level site in the Page Layouts catalog - stored usually as /_catalogs/masterpage/), which functions as a Template to be applied and exchanged (many can be created) whenever needed. Practically, this means that as soon as you ...


2

Aren't they in the masterpage gallery? Can you just copy one from there and insert into your library of choice? EDIT: Only relevant if you're talking code, just seen you're talking 2013, and thus the web interface. In which case there's a Wiki Site Feature to let you create wiki and WP Pages I think.


2

If you don't want to use javascript/jQuery, here's another way to get the left navigation back in web part pages. Create a new web part page Edit the page in SharePoint Designer Remove custom css Delete this code block: <SharePoint:UIVersionedContent ID="WebPartPageHideQLStyles" UIVersion="4" runat="server"> <ContentTemplate> <style ...


2

I would recommend to avoid using id for just css styling, especially such a general word as #current. Use a class instead: .current-page or something like that. SharePoint renders classes and id for a current menu item in the server side. In your CEWP you don't have access to server side. One possible solution is to use an attribute selector with jQuery. ...


2

Web Part Pages live in Document Libraries. The default page in a new site may not. When you create a Web Part Page or a Wiki Page you are creating a document in a special type of Document Library. When you create a site or subsite, it has to have a page by default, but often that page is not in a Document Library. A page in a Document Library gains all of ...


2

The content deployment wizard is one option but you would need to do it 50+ times so probably not the best use of your time. I think your will need to do some sort of scripting against the object model for this to work. Is that a possibility for you? There is SPFile.CopyTo method which is probably what you are going to have to do on the web part page to ...


2

The free edition of CopyMove for SharePoint can do this for SharePoint 2007. The SP2010 version is coming later this year.


2

No you can't. The Web Part and Master Page galleries are site collection scoped.


2

Goto SiteAssets doc library , find the ICV4... page and edit the "Title" field to "Search for Classes" . UPDATE : Goto Site Asset document library settings . Under Content types ,click "Document" . Under "Columns" sections the Title field should be changed to "Required" . It is "Hidden" currently that is why you are not seeing it .


2

Basically, it can be done with css with header and table changing: .s4-wpTopTable { background: #FEE; } .ms-WPHeader { background: #FEE; } If you want to apply this to particular web-part, you can add additional css-marker class on you web-part render methods to find you web part instance later or use js/jQuery-client bases techniques to apply/change ...


2

Since in SharePoint 2013 CSOM API was introduced SP.Publishing.Navigation namespace, the following example demonstrates how to create a publishing page. How to create a publishing page via SharePoint 2013 JSOM function createPublishingPage(pageName,pageLayout) { var ctx = SP.ClientContext.get_current(); var pubWeb = ...


1

if that is the case, please write some CSS to the web part div on the page through CEWP with !important attribute.


1

I think it's whining about the spamdoc.aspx, instead try without the .aspx. Try this instead. $web = Get-SPWeb http://somesite $pWeb = [Microsoft.SharePoint.Publishing.PublishingWeb]::GetPublishingWeb($web) $pageLayout = $pWeb.GetAvailablePageLayouts() | Where { $_.Name -eq "BlankWebPartPage.aspx" } $folder = $web.GetFolder("SitePages") $page = ...


1

I don't have an answer for why this is occurring so I ended up implementing a workaround. A couple of limitations: SharePoint 2013 Online (i.e. No SPD) No deployed code My workaround makes use of jQuery function SetTitle (newTitle){ var $title = $('#pageTitle > span > span'); if ($title){ $title.text(newTitle); // attempt to ...



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