After the branding of a SharePoint site is done, I mean Site and System masterpages, there are still a few pages that uses the default style. My question is if we can change the master page for that pages too.
Example: http:///_layouts/settings.aspx
always looks like a fresh SharePoint
The master page connected to Settings.aspx is /_layouts/Application.master. Many system pages use this master page but none of them use the custom or default master of the site.
Do know that modifying the file isn't supported by MS :)
yes, you can refer your customized master page for those pages.
Related
Like the title says, how can I customize the web dashboard in TFS 2012? I have created my own Work Item Type and would like a shortcut on the home page of Team Web Access. I am using the default Team Web Access page and I would just like to have a shortcut button immediately on the front page instead of in a dropdown, which is where it's contained now.
Thanks!
There is no supported way to do this. In TFS 2015 they have the concept of Web Extensions, but that is only for specific extension points which doesn't include changing the home page.
You can do it in an unsupported manner, but I wouldn't recommend it. You can find the ASPX/CSS/JS files on the server that TFS uses for the web site and hack away at them. I've known people that have done this before. But there are probably repercussions when it comes time to upgrade.
For posterity, I've found a dirty solution to do this without cloning the website and gutting it (as described here: http://awaitwisdom.com/how-to-extend-tfs-team-web-access/). Note that this solution is really dirty and may not fit your project needs.
The solution works by swapping the default work item options (based on the process template you are using).
Use WITADMIN to export your Categories into an XML. Find a work item currently on the front page that you're okay with swapping out for the work item you want to be on the front page. Change "DEFAULTWORKITEMTYPE" to "WORKITEMTYPE" in the tags. Add a new entry: and it should show up as one of the shortcut buttons on your home page.
I highly recommend doing your modifications with Microsoft TFS Power Tools 2012.
I am using umbraco 7.1.3.
My requirement is to create another sub-domain in main site dynamically as per user request.For example I have implemented umbraco cms for my site "ww.xyz.com" & I am updating content through umbraco login. Now I want to create sub-domains for different clients as per their request... like : "www.xyz.com/client1", "www.xyz.com/client2" and so on...
Now all sub-domain site should have it's own umbraco framework, so client-site (sub-domain owner) can login and update their information respectively.
To achieve this requirement I implemented following steps...
First I register a umbraco website in IIS and configure it, and that worked properly.
Then I register another umbraco website in IIS and configured it, and that also worked properly.
Now to implement sub-domain logic...
I simply copied 2nd website's folder in to first website folder. Then convert that folder to application through IIS.
As per my expectation this should work, As I have already done the same in asp.net and it worked.
But with umbraco I am facing issue like "Invalid key value".
I think the issue is related to some umbraco configuration, but I am not able to figure it out.
Thanks & Regards
A bit of an open door, but since I don't see it mentioned in any of the comments and it's a bit hidden away in Umbraco 8. Have you tried setting the urls in the Cultures and Hostnames section?
Note: you get to this by going to "Content", in the content tree right click on your homepage and now you get several extra options which are normally hidden away with also the very useful Hostname and Cultures option which allows you to support multiple urls.
I've created multiple custom application pages using VS 2010 and have deployed them to my SharePoint site.
I'm running into an issue when trying to reference these pages by a URL...
If I use http://myserver/sites/mysite/_layouts/MyApp/MyPage.aspx everything works perfectly, and I can view my pages.
If I use http://myserver/_layouts/MyApp/MyPage.aspx I get a HTTP 404 Not Found error.
Is there a way I can navigate to my custom page by URL without a specific site reference? Everything I've looked at says that I should be able to access this page directly from /_layouts but it doesn't seem to work.
Note: If I look at the folder "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\MyApp" on my server, I see all the aspx pages...
Have you tried another browser? I only have this problem using Firefox, Internet Explorer works perfect. Tried this?
Since the page works on one Site Collection but not the other, it seems to indicate a feature scope issue. However, I'm not sure how this would interfere with pages under _layouts.
Is your application page associated with a Site Collection level (or lower) scoped feature?
If so, is that feature activated on the root Site Collection (http://myserver in your example)? Activating the feature or expanding its scope may well resolve the problem.
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,
George
The page layout is default.aspx's backing "template". It holds the actual controls. Edit page layouts to move around controls etc. You can also create your own and bind them to content types.
Edit in browser basically means you edit the values of say the title control, or the content of a richtext fieldcontrol. This is usually done through sharepoint's front end web UI. You can also change a page's assigned pagelayout to a different one, i.e. have default.aspx use ArticlePage.aspx as pagelayout instead of WelcomeSplash.aspx. THis is done in the publishing console in the web ui as well.
I want to create a master page for my dotnetnuke web application, can u give me guide lines for how to create master page and how to register into dotnetnuke.
DotNetNuke does not use Master Pages. It uses a concept known as "skinning" to create consistent views of your website.
At a basic level, a skin is an .ascx control that has <div runat="server"> in places where users can add modules.
It's not completely up-to-date, but the Skinning Guide document on DotNetNuke.com is probably a good place to start.