I am trying to set Global navigation for my publishing portal site in sharepoint 2013 using Managed Metadata. It works fine for Default.aspx but when I browse to Site Settings page it does not show some of navigations.
My navigation is shown bellow :
Now when I browse to default Page it shows navigation perfectly as shown bellow.
But when I browse to Site Settings page it only shows :
Problem: I have created Top Navigation using Managed Metada Service in Sharepoint 2013. It works fine for all pages such as Home.aspx, default.aspx etc... In other words it works great with WebPart Pages. But when I navigate to any of Application pages e.g. Site Settings or Site Columns( they are called application pages which by default referencing default.master page.), it is not showing my Top Nav bar with all its menu item as well as Sub menu items.
I have googled lot, finally I got solution for SharePoint 2010 from here,
First locate/find PlaceHolderTopNavBar
<asp:ContentPlaceHolder id="PlaceHolderTopNavBar"
and rename it to PlaceHolderTopNavBarOriginal,
I looked into my custom.html page for same div tag as suggested in link above but I could not. After that I find
<div class="ms-hide">
and put
<!--SPM:<asp:ContentPlaceHolder id="PlaceHolderTopNavBar" runat="server" Visible="false"/>-->
inside that div.
I have written blog here:
http://apppagetopnavigation.blogspot.in/
Hopefully this will help you all.
I'm not too sure. But I think that's caused by the fact that they're using different masterpages.
Meaning when the person that activated the cascading dropdowns forgot to make that master page the default for the site. He might have only selected set as custom master page instead of default.
Sean
I think this is a bug it happens in all SharePoint 2013 versions and also in the Office 365, in the settings pages it will always show just one level in the menu.
Related
I'm really finding it difficult to set up a new theme for my SharePoint 2013 site.
I have uploaded all other files to the design gallery. But when I uploaded the page layouts, and I try to change the Content Type to Page Layout, I get the error below:
Sorry, something went wrong List does not exist.
The page you selected contains a list that does not exist. It may have been deleted by another user.
Technical Details
Correlation ID: ce2b429d-0147-d0c2-bc23-32b039f7d8a6
Please what can I do to resolve this?
Thanks.
I got it working by disabling the publishing feature under > site settings > Site Collections Feature > SharePoint Server Standard Site Collection features
Deactivate
Reactivate
Rebooted the server (probably could have done an IISReset but
overkill!)
Now I can add layout pages under master pages gallery.
In the browser, go to your site, and on the Site Actions menu, click
View All Site Content, and then click the Pages document library.
Or you can browse directly to
http://your_site/pages/forms/allitems.aspx, where your_site is the URL
for your site, such as fabrikamweb/finance for the
http://fabrikamweb/finance subsite.
The Pages document library is created automatically by the publishing
feature and contains all of the pages in a site that are created from
page layouts. You can look in the Page Layout column to see which page
layout was used for a specific page and then click the link to view
that page in the browser.
https://support.office.com/en-us/article/Customize-a-publishing-page-layout-c10bda25-0145-44c6-ba14-7757176fb47f
I want to customize the SharePoint 2013 online(office 365) "About me" linked page (personimmersive.aspx) to a custom look and feel.
Even clicking on any SPUser name, for ex in a list item modified by is "John Smith" if we click on it goes to about me page.
This page resides under mysite but I cannot see this page is SharePoint 2013 designer to edit, but modifying SharePoint pages in designer is not always the best way.
Can I just create a new page and redirect all Profile page request to that custom page?
IF I create app parts and edit the page I cannot edit the top portion of the page.
redirecting may not be a feasible approach, specially on the online versions
you can try to take advantage of web parts and css to do what you can
The biggest change is that you can’t edit the entire top portion of
the page. These used to be in a web part zone, and you could choose to
add/remove the web parts. Now they are fixed, with no ability to move
them around or change the parts.
We had removed the Activity Feed web part previously because we were
using Yammer newsfeeds and group feeds embedded throughout the site,
and this part always showed “No activities”. Now this is back again,
with no way to remove it, short of editing the page in SharePoint
Designer.
There are still web part zones on the bottom, but really the problem
is no control over the display of most of the top of the page.
http://weshackett.com/2014/04/office-365-new-profile-page/
There is personImmersive.aspx in SharePoint Designer, you should be able to find it in All Files. Just make sure you connect to [your_domain]-my.sharepoint.com instead of [your_domain].sharepoint.com.
you can't customize the page completely.However you can add custom web part and custom css to change the look and feel to a great extent.
#tiago duarte you can still remove the activity web part.This can be done using script editor webpart and hiding the complete block/div.
I faced an interesting problem. I have a sharepoint 2007 website. I created a new masterpage and changed default design. So i dont use default.master.
I add site actions menu to masterpage. it renders on google chrome successfully. But there is a problem on IE. I cant see a div or text related with site actions menu on html source of IE.
So what could be reason of this problem?
I am almost sure that this is a probled related to unattended removal of some javascript from master page that handles IE compatibility.
Try to compare your master and the default one and to play with removed lines.
I'm working on creating a reusable and extensible web application in SharePoint 2010. I've created a master page to apply across all pages in the site. However, whenever I create a web part page and navigate to it, the site icon does not display. Instead of my custom site icon being displayed it shows the default SharePoint icon. I can get around this by placing the icon directly into the master page, but that would require me to create a new master page if I ever wanted to extend this web application.
Does anyone know why this is happening? My initial thought was that the web part page had somehow been customized to not use the default master page, but that does not seem to be the case: if I update the master page it is reflected in the web part page.
Googling around and checking this site yielded little answers. I only found one post out there that reported the same issue I am observing but there was no solution.
If it helps, I did notice one phenomena when navigating to this page. Before the page completely loads, the correct site icon appears for a split second before being replaced with the default site icon. Hope that helps.
I ran into the same issue this morning and didn't want to create a custom master page just for this, but luckily it was quickly resolved by following admlcrunch's suggestion (on SharePoint 2010):
Go to the desire page
Click on the "Page" tab at the top
Click on the "Title Bar Properties" at the right (in the ribbon)
In the Image Link section on the right, paste in the image URL
Click OK
The only bad thing about this is, you have to update every Web Part page that you want custom icon image to display.
I was just having the same issue. Web Part Pages have their own icon that you can set.
To set the icon click Page > Title Bar Properties. This will open the Web Part Page Title Bar dialog. In this dialog there is an area to set the Image Link. You can set the icon here. I just copied the URL to the site icon.
Open the page in designer and remove the custom titlebar place holder:
[WebPartPages:TitleBarWebPart]
from the :
[asp:Content ContentPlaceHolderId="PlaceHolderPageTitleInTitleArea"]
I have a custom feature which adds a few controls into the AdditionalPageHead DelegateControl. This works fine on any sites which use our default.master. However the project requires the use of a publishing site which has a master page derived from BlackBand.master (which does not have the AdditionalPageHead DelegateControl included), so I made a copy of the master page from the master page gallery on the appropriate site collection and then modified it to include the following line:
<SharePoint:DelegateControl
ID="DelegateControl1"
runat="server"
ControlId="AdditionalPageHead"
AllowMultipleControls="true"/>
This should therefore include this DelegateControl within all pages using this master page. However when this is uploaded as a new version of BlackBand.master and approved as such, all the pages in the site that use it get a 404 error as if they no longer exist. If I restore the previous version of the master page then everything return to normal.
Help is appreciated as always.
The answer was that I was approaching the solution to my problem incorrectly.
To fix this I opened SharePoint designer at my site collection root and clicked on _catalogs/masterpage. Then I made a copy of BlackBand.master in the masterpage catalog. Opened it and added my line of code. Saved it and then set it as my default and custom master page (to ensure that it applied to any straight up web part pages as well as layout pages).
This worked without a problem.