Tag Info

New answers tagged

0

I am answering on the assumption of this being an on prem environment. everything from the read, e.g. "A week ago it worked perfectly", "Clearing cache and/or refreshing the page do not change results" makes me immediately think about load balancing problems. try removing the cache on the frontend balancers level, perhaps it will help, as it did for me


-2

Try checking for duplicate urls in your list of links


0

Absolute links to subsites that don't exist are treated as relative, but those that point to existing subsites work correctly. The trouble is that this doesn't change once the missing subsite has been created, so the trick is to actually remove the link and create a new one (even though its text and URL are just the same). This seems silly, so I'm not going ...


1

Use "../yoururl/targetlocation", with those two dots. Edit: Or you could also use the complete URL, e.g. http://sitecollection/subsite/


0

Fixed this problem, instead adding new controls, I just used paddings and margins, plus, I hid iframe which created white background (needed IE specific css): -ms-filter:"progid:DXImageTransform.Microsoft.Alpha(Opacity=0)"; filter: alpha(opacity=0);


0

Is the "Use this Term Set for Site Navigation" checked? You find this option in Term Store Management Tool.


0

IMO there should be nothing you can't do with CSS. You can fairly easily discover and override default CSS styles and take advantage of selectors to do and undo styling throughout the markup. However, there are other approaches, in case you want to go that way: UseSimpleRendering JQuery.wrap()


0

Just to share some code, this is how I got around the issue and it works perfectly. The code below would go inside a $(document).ready() function //About the following block of code //Because of SharePoint MDS, SP doesnt like appending data to the querystring of a navigation item. //If a navigation item has data appeneded like a ? or #, it gets stripped ...


-1

Set your button type to button. By default on the asp page your button is type submit This was my post above


-1

Set your button type to button. By default on the asp page your button is type=submit


0

I would try selecting "include content" when saving the template. You may also want to try importing the template into Visual studio to poke around with it and see if the nav content is actually getting saved.


0

if you do not need another html structure or rendered Information than the default sharepoint navigation, then it is recomended to brand it using CSS and JavaScript. Otherwise you have to create your own control. In your Control you can use the default sharepoint navigation control with a default or custom Site Map Provider. This example shows howto build ...


0

Manually-added relative URLs are security trimmed.


0

Have you tried to use managed metadata. 1. create a new Global Term Group called Global Navigation. 2. Createjavascript and placed inside Style library folder Function.registerNamespace('Mavention.GlobalNavigation');   Mavention.GlobalNavigation.MenuItem = function(title, url) {     this.title = title;     this.url = url; };   ...


0

Sorry I can't post code right now, but if you are still having a problem next week, I'll post back. I created a plugin awhile back to do this: make elements sticky. It supports sharepoint and I'm currently using it in SP2013 (o365) with a few small apps. The plugin is: http://purtuga.github.io/jquery.stickOnScroll/ You will need to use the set the ...


1

I found out that I need to use another control to achieve the results I wanted. With this snippet inside the page layout (eg inside the PlaceHolderPageTitleInTitleArea placehoder) it renders me the path nicely to the current page/element: <h1 id="pageTitle" class="ms-core-pageTitle"> <!--SPM:<asp:ContentPlaceHolder id="PlaceHolderSiteName" ...


1

The relationship between .html and .master is a bridge. It has been implemented so that developers who are not familiar with ASP.NET masterpages and SharePoint can use the .html file to do the changes in a "environment" they are more or less familiar with. I'm going to assume this is an on-premise solution, so yes, downloading and putting the .js file in ...


1

Please try this Response.Redirect("PageName.aspx"); Or Response.Redirect("/SiteCollection/Site/SitePages/PageName.aspx");



Top 50 recent answers are included