SharePoint page edit issue

George2
  • SharePoint page edit issue George2

    I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise, and I am using publishing portal template.

    I am using SharePoint Designer 2007 to design pages. When I open the default.aspx under Pages sub-folder of a site, there are two options:

    • Edit in Browser and
    • Edit Page Layout.

    I want to know what are the differences between Edit in Browser and Edit Page Layout -- especially what is the function of Edit Page Layout, because when I select Edit Page Layout, WelcomeSplash.aspx opens in SharePoint Designer, other than default.aspx itself (very confused).

    thanks in advance!

  • Publishing pages have a PageLayout associated with them so they cannot be edited in SharePoint Designer directly unless you unassociate it with the Page layout. So when you get the option "Edit in Browser" basically is the same as selecting "Edit Page" from the site in which you move around web parts, and "Edit Page layout" will allow you to restructure the underlying layout which would impact any other pages that use the WelcomeSplash layout in that site collection.

Related questions and answers
  • I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise. I am using SharePoint Designer 2007 to open default.aspx under Pages sub-folder (selecting edit page layout in SharePoint designer 2007) of a site, but welcomesplash.aspx displays other than default.aspx itself, why?

  • I am using Search Server 2008 based on SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise. I have tried the search function by using IE to access address http://<machinename>, and everything is fine with search functions (e.g. I can search page content by keywords). Now I want to use SharePoint Designer to customize the page. But when I use SharePoint Designer to open http://<machinename>, I met with warning that the site is protected by password; And when I use SharePoint Designer to open http://<machinename>/default.aspx or http://<machinename>

  • I am using SharePoint 2007 Enterprise + Publishing portal template + Windows Server 2008. I am developing using VSTS 2008 + C# + .Net 3.5. I need to implement SSO (Single Sign On feature) with another site. The SSO protocol is like this, The other site will send me information like http://mysitename/default.aspx?Identity=abc or like http://mysitename/default.aspx (mysitename is the site which I am developing); If the value Identity variable is null, it means anonymous user. And if the Identity value is not null (means an authenticated user), I will using a WCF interface to find user

  • I am using SharePoint 2007 Server x64 on Windows Server 2008 x64. I create a new SharePoint web application with a new site collection at the root of the web application. I select the template... users who have not logged in yet) of the site. Here is a screen snapshot. Any ideas how to edit this page? Publishing home page http://i33.tinypic.com/2hex08j.png BTW: I have tried to edit... on the site collection for the forms authentication logon page to work from Office SharePoint Server. Contact your administrator to have anonymous access enabled in Central Administration and IIS. Manage

  • Are there any "gothchas" when upgrading workflows from 2007 to 2010: In place upgrade on server Conversion of VS Solution What happens to running workflows?

  • I am using SharePoint 2007 Enterprise + Publishing portal template + Windows Server 2008. And I am developing using ASP.Net + C# + .Net 3.5 + VSTS 2008 on SharePoint Server 2007. I am developing... is, when a user access a page for the first time in my SharePoint site which needs authentication, if there is a special URL variable in current http session called "Identity", I want to treat the user as authenticated user and using the value of the "Identity" URL variable to be the authenticated user name of SharePoint (for example, accessing my SharePoint site by URL http://mysite/default.aspx

  • I am developing a company website/portal in SharePoint, and am trying to figure out the best way to organise it into site collections, sites and subsites -- I'm confused by the terminology I think. The site has a public-facing Internet presence which is to be managed via the Publishing WCM features of SharePoint. Behind the scenes there will be some portal features, such as personalised... again be in a separate site collection. I guess my general question is, what are the rules of thumb for when to use a site, when to use a subsite, and when to use a site collection?

  • I am using SharePoint Server 2007 Enterprise with Windows Server 2003 R2 Enterprise. I am developing using VSTS 2008 + C# + .Net 3.5 + IIS 6.0. I have put a simple aspx page into layout folder (the code is very simple, just redirect to another page, and I write inline script code in asp.net), here is my code, and I met with unauthorized error (403) when I select to browse the page from IIS 6.0 manager. I am not in Active Directory or Windows domain environment. I have enabled permission to anonymous users for the whole SharePoint site. Any ideas what is wrong? <%@ Page Language="C

  • I am using SharePoint Server 2007 Enterprise with Windows Server 2008 Enterprise, and I am using publishing portal template. I am using SharePoint Designer 2007 to import a list to a web page by using Data View -> Insert Dataview, I find when the list is from the same site, it is ok; I find when the list from child site, there is error like (I drag the list directly to get all the content, no additional sub-filter on the list), The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again. If the problem

Data information