Hot answers tagged web-part-page
6
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 ...
5
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 ...
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>()
...
3
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 ...
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 ...
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
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 ...
1
I find it depends on your content. If your pages are going to be really text heavy, and you don't need much flexibility in terms of placement of your web parts, go with the Wiki Page. Wiki Pages allow direct text editing without the need to keep dropping Content Editor Web Parts.
Web Part Pages have more options in terms of web part layouts (in the form of ...
1
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)
...
1
Yes it is possible, only users with Full Control, Design or Contribute permission can only add or remove webparts as demonstrated in picture below,
Source
Don't forget about custom permissions levels.
1
If you are using JQuery this function just should be loaded in
$(document).ready(function()
{
// Handler for .ready() called.
});
Here is the link to definition
Hope it helps,
Andrew
1
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. ...
1
This is more of a general HTML/CSS question (except for the fact that you are using CEWP), however, while you are still here why don't you Export the CEWP and simply use a selector (e.g. id="current") and define that with the style for the active one, while changing which of the elements have the #current added on each page.
On the other hand the top ...
1
AFAIK Save File Dialog, Open File Dialog are form controls and not web controls... So they will not work in Web environment!
You can use normal File Download code to let the user download the file and select where to save, see below links:
Download a file into client with ASP.NET 2.0
File Download in ASP.NET C#
Once you have the byte[] of the file, write ...
1
There are 2 types of "pages" that SharePoint uses in Lists/Libraries:
views - such as in AllItems.aspx
Forms - DispForm.aspx & all.
The one you are referring most likely is the default view, such as in AllItems.aspx. One thing you could do is to enter that page in edit mode (append PageView=Shared&ToolPaneView=2) and add any other web parts (note ...
1
You can have webparts that don't show up in the menu. If you don't deploy the .dwp or .webpart file to the webpart gallery, then your webpart won't show up.
I have a few admin webparts that I do this way. I just keep the .dwp or .webpart file on my local computer, and when I need to use them I just upload the file to the page and configure it.
You can ...
1
Unfortunately in the list of permissions the permission in charge (for SHARED Views) is called which enables all these actions: "Add and Customize Pages" - Add, change, or delete HTML pages or Web Part Pages, and edit the Web site using a Microsoft SharePoint Foundation-compatible editor.
You could restrict to ADD-ing list Items only, using a Permission ...
1
If you want to limit width of a section irrespective of its inner content, Try using <div>
See this as example : http://www.techrepublic.com/article/creating-a-fixed-width-layout-with-css/5314471
1
A sandbox by design is scoped inside of a site collection, and has no direct access to the GAC or the 14 hive (where the file would be ghosted).
Therefore the file will be stored in the site collection database.
The only performance hit would be the redundant files in multiple content DBs increasing disk usage but for these templates I don't see it being ...
1
Looks like it is possible. I had to handle my Module element a bit differently. The key was to add a List="119" (for the Wiki Page Library), a Url="SitePages" to the Module. Then in the File elements, ensure Type="GhostableInLibrary" is set.
I found this resource which helped me come to this conclusion:
...
1
This isn't a definitive answer, but it seems to be faintly related to creating more than one view bearing the same Title. After I rewrote the relevant code to remove previous versions of the the view in question, this exception disappeared.
Chalk this one up to circumstantial evidence.
1
Sub-site: A sub-site (or a site) is like a box with a lid. What you put into the box stays in that box. You cannot mix what is in that box with material from another box (site or sub-site). For example, if there is a sub-site A and a sub-site B. You will notice that a webpart (e.g. a library) set up in sub-site A cannot be added to sub-site B. They ...
1
Pages(basic or webpart pages) themselves are inherently part of a site(or sub-site in your case) collection in SharePoint. They inherit their permissions from the site that the page gets created in.
Here is a quick overview of pages vs sites:
...
1
I hope your Mobile.aspx is an Application Page. In application pages, you can set the master page either in the .aspx with the MasterPageFile attribute:
<%@ Page Language="C#" AutoEventWireup="true"
CodeBehind="ApplicationPage1.aspx.cs"
Inherits="SharePointModalDialogDemo.Layouts.SharePointModalDialogDemo.ApplicationPage1"
...
1
So, it seems the Module is necessary and has to be correctly configured. Most of my problem above was not knowing about having a Module, and the rest by not having it set up properly.
Here are some useful links on the matter; a mashup of which I used the create the eventual solution:
How to: Deploy a Web Part Page in a Sandboxed Solution
Module Element ...
1
It sounds more like what you need is a Site Template.
Please explain how your document Library is setup. Have you setup actual web parts on the different views of the doc library?
Example: Allitems.aspx has a couple of webparts, NewItem.aspx has a couple of webparts?
If so, saving the doc lib as a template should work.
If not, and you created normal ...
Only top voted, non community-wiki answers of a minimum length are eligible
