Kentico domain aliasing - Default Path option - kentico

I'm retrofitting a V9 site with a new 'sub site' This site will have it's own navigation system and IA. My plan, maybe, is to create a new folder in the content tree named 'New Site' and then created all my pages and items within there.
For the domain, i would then create a domain alias, and set the 'Default Alias path' to the 'New Site' folder.
This so far seems clear. Is it possible to have cross site contamination? Ideally, the old and new sites wouldn't mix under a single URL. I'm worried about navigation on the old site ('css list menu') picking up pages from the new site.
Had i know this was the plan, i would have created folders for each site to isolate, but moving to that structure may cause a lot of problems.

Based on the answers you posted, what I've done in the past is to:
create a new page type called Divisions or whatever you'd like.
Then create a new page template which doesn't inherit anything from the master page and flag it as a master page. Add the webparts you need on there, specifically a Head HTML webpart with your stylesheets, js, etc. Because it won't inherit from the main master page. But if you have a stylesheet assigned in to the site in the Sites application, that will be inherited unless you specify otherwise on the General tab of each new sub site.
Back on the page type you just created set the default page template to be the master page you just setup.
Add a new sub site/page to the content tree
Add new pages under the sub site in the content tree. Set your navigation path to be /{0}/% so it always selects the sub site as the root.
In your other master page you shouldn't need to worry about the other pages, because the parent page won't be visible in the navigation so the children won't show.

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.

How to redirect one page to a different URL than the rest of the HTTP redirect IIS8

First off, apologies for not knowing the nomenclature for what I'm looking for, I'm not typically a Windows web admin.
I have a SharePoint website which contains several subsites. We also have several alternate URLs that point to specific pages, and some of those alternate URLs have friendly URLs which also redirect to other specific pages. We're in the process of migrating from a SharePoint 2007 site to this one, and in the process, I'm trying to remove our reliance on our registrar for handling some of this redirection, because it is apparently not a free service.
Currently our registrar does the following redirects:
http://alias1.tld/* redirects to http://subsite1.ca/page1
http://alias1.tld/friendly redirects to http://subsite1.ca/page2
http://alias2.tld/ redirects to http://subsite1.ca/page3
I know I can accomplish the first and second by setting the sites up in IIS, and using the HTTP Redirect function, but I'm not sure how I can do the second one. In Apache this would be easy, but I'm not sure what I'm looking for here.
Is this something that should be handled within SharePoint, and have that take care of redirecting alias1.tld/friendly to the specific page, or is this something I need to setup in IIS? Is this what URL rewrite is for, or is there a different IIS way to do this?
I'm not sure that this is the best way to do it, but I got things working how I wanted them. Here's what I ended up doing:
Create a new subsite on subsite1 to give me the URL subsite1.ca/subsubsite
Create a redirect from alias1.tld to subsite1.ca/subsite
Create 2 pages for the new subsite. One for the default page and one to use to redirect to page2. Both pages are redirects, Default points to Page1, the second points to Page2.
Set the subsite to use Managed Navigation for global and current through Site Settings > Navigation, and created a default term set by selecting the new subsite in the list and then clicking Create Term Set, then clicking OK.
Then created a term store for the one page that needs to be handled differently by going to Site Settings > Term Store Management. Click on the Term Set created in the last step, then select New Term. On the Term-Driven Pages tab, create the friendly URL and then select the target page, which is the redirect page created in step 3, then click Save.

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.

Links on SharePoint 2010 Master Page not changed based on Alternate Access Mappings

We are creating a custom branded Master Page in SharePoint 2010. To make the page similar to a legacy page we have implemented an html based custom dropdown navigation menu we had in place directly on the Master Page (consisted of basic HTML elements ULs and LIs with A tags styled with a CSS class).
I assumed the links from the basic HTML on the page would be subject to Alternate Access Mappings currently in place, but it seems to not be the case. On a test page opened in 3 different URLs (http://sharepoint2010, http://sharepoint2010.mydomain.com, https://sharepoint2010.mydomain.com) the links from a WIKI page are modified as I expected, but the links from the Custom Navigation Menu (plain HTML on the Master Page) are not modified.
I can see where that would be useful... But is there a way that I can add links on the MasterPage in a way that SharePoint parses them first, making them subject to Alternate Access Mapping translation? I tried placing a link inside a SPLinkButton control, but it didn't achieve the desired behavior.
e.g.
<ul id="navmenu">
<li><SharePoint:SPLinkButton runat="server" NavigateUrl="http://sharepoint2010">sharepoint link</SharePoint:SPLinkButton></li>
<li>sharepoint2010</li>
<li>test</li>
</ul>
When I access the page via https://sharepoint2010.mydomain.com the links above are still http://sharepoint2010 rather than https://sharepoint2010.mydomain.com
Any thoughts?
Thanks,
Victor
EDIT (clarify):
I was planning on using relative links as a fallback. But for the purpose of what we are doing it would be more maintainable if we could keep the full links and use AAM.
I'm aware that standard relative links are a possibility. I was hoping to identify if there is a way to use AAM on Master Page content (or even on Content Retrieved from External Services down the road) by providing a specific link syntax, or control framework.
There is no need to re-insert the host name if your links are on the same domain and you're not using managed paths. Keeping your links relative will ensure that any bindings in IIS and AAM setup in SharePoint will work without any additional work.
Otherwise, I would heavily suggest to use the available ~sitecollection and ~site SPUrl token to retrieve the current site collection url or current web url. You need to wrap it in anything running server side as the expression will be handled ... server side.
eg:
<asp:Literal runat="server" Text="<% $SPUrl:~site/press-releases/ %>"/>
Hope it helped
When you use the NavigateUrl= attribute of the SPLinkButton, SharePoint renders a simple anchor with href= instead of regular PostBack JavaScript code. Alternate access mapping do not play a role here.
If its simply relative links you want, then leave out the dns entry altogether (ie the bit of the url you are switching with your AAM) and begin the url with a forward slash to make it relative. If this doesn't meet your needs, the way Sharepoint does it is with a relative url token. Have a look in v4.master for the tilda character followed by 'site' or 'sitecollection' which refers to the current web and site collection respectively. Copy this method. For more details, look at this link: http://msdn.microsoft.com/en-us/library/ms473643.aspx

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