I have encountered the following problem in Sharepoint 2013: when I go to Site Settings -> Look And Feel -> Navigation the Show pages option below Structural Navigation: Display the navigation items below the current site is greyed out and cannot be selected.
I have enabled the SharePoint Server Publishing Infrastructure feature and I am working with the top-level site.
I tried to check Sow pages from within a subsite but it's also greyed out.
Can you help me solve the problem?
Thank you in advance.
LATER EDIT
I've also enabled Sharepoint Server Publishing from Site Settings->Site Actions->Manage site features and now it's working
Related
I have created a "Team Site" on SharePoint online. When I edit a site page, I am not able to view any option of adding a web part on the page. All I can see are following options. Please click the link to see the options. I don't see any web part option there.
I believe there are some features that need to be activated on this site collection. Does anybody know which features need to be activated here to enable web parts on the page?
Unfortunately, WebPart doesn't work in New Experience. You need to be in Classic View to add the WebPart.
You can't add web part to New experience mode Sharepoint page. At least not for now. But you can create a page in Classic mode, it's the same as it was in SP2013.
How to do it - Read this article
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 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.
I'm taking over a SharePoint portal and noticed the previous developer used SharePoint Designer for all of the development whereas I use Visual Studio custom solutions/features for development.
NOTE: Site Publishing Features are enabled on a Team Site template for some web applications.
The issue I've noticed is the v4.master content type was changed from "Master Page" content type to "Page Layout" content type. This must have been done through the "Edit Properties" on the publishing site. When opening the site in SP Designer, the v4.master shows up in Page Layouts instead of Master Pages.
The v4.master also has the blue icon next to it meaning the page is customized and content is stored in the database which is causing performance issues. SharePoint is so slow that users are very frustrated. Also there are script tags in the masterpage pointing to jquery in the top level scripts directory. Personally, I would of created a delegate control for this instead of customizing the v4.master. NO Copy was made. (I totally dislike SP Designer, this tool gives too much power to inexperienced power users that like to put sharepoint developer on their resumes. I am definitely disabling SP Designer)
So, with all that said, what are the best practices or suggestions if any in fixing this issue?
What issues will this cause for future applications or site collections?
Should I develop and deploy a custom master as a feature then "Reset to Site Definition" on the v4.master?
Why does SharePoint allow users to change the Content Type on a Master Page to "Page Layout"? Why is this even an option, it doesn't even make sense?
All you need to do within the SharePoint Designer is publish the master page in the page layouts folder and approve it in the Master pages and page layouts in site settings. The master page will appear in the master pages section in SharePoint designer.
I'm using MOSS 2007 with Publishing Site and have added an Image Web Part to a page using Sharepoint Designer.
When I go into the browser to edit the page, the edit button on the web part does not appear.
Does anyone know why?
To edit a webpart in a browser it needs to be inserted inside a Web Part Zone, try adding one in your page then adding the webpart to it. If still no luck or if you already have a Web Part zone, go on its properties (right click => Web Part Zone Properties) and see if users are allowed to edit it in browser.