Restore SharePoint publishing homepage to Pages/default.aspx - iis

I have a Publishing site and the last SharePoint administrator copied /Pages/default.aspx to /default.aspx and set it as the homepage, so now I have two independent copies of the same page to maintain.
I want to delete the /default.aspx and reset the HomePage to /Pages/default.aspx. I can set the "Welcome" page back to /Pages/default.aspx through the settings page, but the /default.aspx page still shows as the homepage in SharePoint Designer. When I try to rename or delete it warns me that I'm deleting the homepage and x numbers of links point to it.
Any suggestions on how to effectively do this?
Should I set the welcome page and change the /default.aspx to a redirect page or just delete it?

Related

Sharepoint 365: Set the site contents page as the home page

Is there a way to set the home/landing page for a SharePoint 365 site to the Site Contents page https://support.office.com/en-us/article/The-SharePoint-Site-Contents-page-ba495c1e-00f4-475d-97c7-b518d546566b
You could add a script on startpage in a script editor web part that redirect users to Site contents. That redirect surely will create a "flicker".This should do it:
window.location.href = "/_layouts/15/viewlsts.aspx";
Beware that this will be hard to remove from the web part (you will always get redirected), so maybe it should be added to a new page layout that is used by the startpage. Then it's possible to edit/remove the redirect through SharePoint Designer.
You could also try (if you have publishing feature activated) the "Welcome Page" link in site settings. Maybe there you could somehow point out the path to site contents, but I doubt it.

Default to index page when navigating to a Document Library in SharePoint 2010

I have a public internet site created in SharePoint 2010. I have uploaded an index.html web page to a Document Library, which I will call "abc." Here is what I want to happen:
www.website.com/abc >> should automatically direct to index.html in that library.
Instead, when I go to that URL, I am asked to log in. My usual login information that I use to edit the site, however, has no effect, and I am eventually just taken to blank white page.
If I type the full URL, www.website.com/abc/index.html, it goes to the correct page, so I know it has been published.
The index.html page is the only item in the document library.
The web address listed in the Document Library settings is http://www.website.com/abc/Forms/AllItems.aspx. I think this is what I need to change to get it to default to index.html. Anyone know how to do this?
Thanks.
Sharepoint document libraries can only have default views for their default pages. Can you create a view to make your changes there, or edit the default view?
If not, you could always edit the default view in Sharepoint Designer and put a redirect to your page, but that's kind of hackish.

Sharepoint: Redirect user to default site

Is it possible to set a default site for a group of users in Sharepoint and have the main default page redirect them to the sub site?
I don't know an out of the box feature which could do this, but you could write a small WebPart which does the redirect depending on the user who visits the site. Shouldn't be to difficult.
The configuration could either be stored in the web part itself or within a list. To speedup the whole redirect process you should cache the redirect information when it was read from the configuration.
That's the way I would do this.
Don't forget to think about a way which let you access and edit the page with the redirect web part without getting redirected.

Browsing a SharePoint publishing page returns a 404 error message

I've changed the master page on a publish site collection. When I browsed back to the start site to check the new master page the browser just returned a 404 error, telling me that the page could not be found.
But when I open the site collection with the SharePoint Designer every thing seems to be ok and in its place. All pages are as expected in the page library. Within the Designer I could even open the pages for editing.
So does anyone has an idea why the browser cannot find and open the pages?
UPDTAE
To clarify my problem I should say, that also switching back to the default master page doesn't bring back the site. I still get a 404 response. So the problem shouldn't be directly related to my custom master page.
Approve the Master Page ?

Why can't I override the default master page content in a SharePoint publishing page?

So I've setup a site collection using the Publishing Portal template and stubbed out a prototype site structure including three tiers. At the second tier I've created a Publishing site and developed a custom master page for the site and its third tier children. The problem is that the banner graphic on a few pages should be modified to be inconsistent. Then I add two new ContentPlaceHolder controls to my master page in SharePoint Designer and use the SharePoint interface to create my new publishing pages. Finally, I verify in SharePoint Developer that they have the correct master page, add my asp:content controls to the pages and insert the page-specific banner graphic. The only problem is that the master page default content continues to be rendered in all page instances. If I create a new page from the master page in SharePoint designer, I get a different base class in the Page declaration than those created within the Publishing site. Do publishing sites ignore any non-SharePoint contentPlaceHolders?
There is nothing like SharePoint ContentPlaceHolders & non-SharePoint ContentPlaceHolders. When you add a Default content to the Master Page ContentPlaceholder and if you dont override it in the Content Page then it will be visible in all the Pages that use that Master Page. Only way to get rid of it is to Override those Content Place Holder with empty content in the Content Pages. As overriding contentPlaceHolder in all the Pages is not an good Aproach. What I recommend is not to place conent in the ContentPlaceHolder of the Master Page but instead , put the content in the Content Control page of the Pages, so that Content doesn't come in all page but only the page that needs it. Yes it not a good to put the exact same content in multiple page. but in your case that is only the Option. May be you try to wrap the content in to a User Control so that the code can be updated only one place

Resources