Has anybody any sample code or excellent article links showing an implementation of a breadcrumb navigation into a SharePoint 2010 Website?
Technet says this
Breadcrumb navigation displays a dynamically generated set of links at the top of Web pages, to show users their current position in the site hierarchy. By using SharePoint Designer 2010 or Visual Studio 2010, you can configure the breadcrumb navigation control. For example, you can specify a custom navigation provider, and you can remove breadcrumb navigation from a page layout.
This article discusses creating a custom navigation provider.
This is a control that you can add to sharepoint found on CodePlex (mavention)
OK,
here is a short HowTo for the mavention-breadcrumb deployment.
I had some problems doing it the way it's described on the blog and asked the developer for help.
So
1) copy the maventionsimplesitemappath.wsp solution to your website's BIN-Directory
2) add the wsp-solution over the sp_powershell (stsadm -0 addsolution …)
3) GoTo central server administration/farm solutions and deploy the solution we just added before
4) open the website's masterpage in sp_designer(or other) and insert the register- and control-code (you can copy/paste it from the blog above)
that's it!
If you still got porblems with permissions like I had some days ago try this(tipp from the solution-developer & blog owner)
open the website's web.config and search for the line <trustLevel name="WSS_Custom"..
open the policy file you can find in this line (wss_custom_wss_minimaltrust.config)
find lines <CodeGroup ...> maventionsimplesitemappath.wsp should be mentioned here </CodeGroup>
<CodeGroup class="FirstMatchCodeGroup" version="1" PermissionSetName="Nothing">
change the PermissionSetName to "FullTrust" if it's on "Nothing"
hope your permission-problems are solved now
Related
Here i have a issue with SharePoint Designer 2013, an Modern site page was build on SharePoint Online. But i need to customize the modern page and adding url to quick links.
Though modern page doesn't support CEWP or SEWP it's hard to custom the page. But what i am looking is to edit the site pages from SPD 2013 and if i edit the planner.aspx will changes save, unfortune i have Url to navigate the user from the one page to other url(https://...Planner.aspx).
What i want is when user clicks on above link, it should open in new tab and i have to align the page with Css branding. i am adding something like this to open in new tab using SPD href="/abc/xyz/3/SitePages/Planner.aspx?web=1 target="_blank" but no luck at the end.
Looking for an solution, Thanks in advance !
As far as i understand, using SharePoint Designer is not supported for modying the SharePoint modern experience.
You should be using the SharePoint Framework to modify your pages, you can see the full list of supported modifications here:
https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/modern-experience-customizations
However, if you are used to using CEWP and SEWP, you can deploy an app which replicates the functionality in the modern pages
https://github.com/SharePoint/sp-dev-fx-webparts/tree/master/samples/react-script-editor
Atlthough this is probably not supported either, it should allow you to make the changes you want.
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
Hy,
I use SharePoint Foundation 2010 and I learned that the "target audiences" are disabled on the Foundation version.
I need to customize a WebPart on a wiki page when A user of a certain group is connected.
Have you an idea ?
Thanks
Sam
Alternatively you can add a new web part page in your SharePoint site
and then add this Documents web part on the page. Once it is done,
Give access to only intended users for this page. Which means control
access at page level.
source
I have found a solution.
I insert JavaScript code in a WebPart in my wiki page from my SharePoint.
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.
Using Sharepoint Foundation 2010 I've edited v4.master, added a ref to a new CSS file, saved the changes and they are applied to the home site no problem.
However when I create a subsite it uses the old version of v4.master for some irritating reason. I'm vaguely aware that some of the publishing features from SPS are not included in SPF so lots of the online advice isn't relevent (?)
If there is a way to make new subsites inherit the new V4.master I'd be very grateful.
This is only possible with a custom WSP or an HttpModule, both requiring .NET code. The Server versions of SharePoint handle this easily with the Masterpage option, a quick google search for "foundation masterpage solution" gave good results, including:
http://blog.thedesigndrifter.com/?p=1112
http://rickhilferink.wordpress.com/2011/01/25/creating-a-sharepoint-2010-foundation-masterpage-solution-and-automatically-activate-it-for-all-sites-and-newly-created-subsites/
If you'd like the ability to have a master page at the site collection root inherited by subsites, then you are best off using a publishing site template.
You can then go to: /_Layouts/ChangeSiteMasterPage.aspx and specify your custom master page, and have it inherited by all subsites.
this is probably too late to benefit you, but maybe it will benefit others. I have found that if you do not rename the customized master page to something other than v4.master, then subsites will not inherit the customized version of v4.master but use the original uncustomized v4.master instead. So make sure that you make a copy of v4.master and rename it. Here are some steps from [my blog post], this is how i did it:
Right-click on v4.master and select ‘Reset to site definition’ and the original v4.master will be restored, and SPD 2010 will automatically create a v4_copy(1).master page (screenshot 14).
Check-in custom.master, publish a major version, and approve the file
Go to Site Actions > Site Settings > Master Pages and select the new master page, custom.master, for both Site Master Page and System Master Page, and select the checkbox for ‘Reset all subsites to inherit this alternative CSS URL’ (screenshot 15)
Now if you have forgotten to activate the publishing feature for you new subsite with the Team Site template, it will not inherit the custom.master page yet, so go to Site Actions > Site Settings > Manage site features and activate the publishing feature (screenshot 16)
As soon as the feature is activated you should see the new master page and its styles (screenshot 17)
I solved this problem by creating new a custom site defintion by Visual Studio and SharePoint Site Definition. I added a feature which adds my custom masterpage (edited from
v4.master) into site collection's masterpage gallery (_catalogs/masterpage):
<Module Name="MasterPageModule" RootWebOnly="FALSE" List="116" Url="_catalogs/masterpage" >
<File Url="mymasterpage.master" Path="MasterPageModule\mymasterpage.master" IgnoreIfAlreadyExists="TRUE" Type="GhostableInLibrary">
<Property Name="ContentTypeId" Value="0x010105"/>
</File>
The main thing to get the same masterpage for all sites is to set MasterPageFile -property in Default.aspx like this:
MasterPageFile="~sitecollection/_catalogs/masterpage/mymasterpage.master" - this refers always to rootsitecollection level.
I think that same thing can be achieved by using FeatureActivated-method, but it didn't worked in my case, don't know why.