User Profile
RichardSharp11
Brass Contributor
Joined 10 years ago
User Widgets
Recent Discussions
Re: Onedrive and Sharepoint still configuring after 24 hours.
I see this occasionally. I always tell people to use some browser other than Chrome for the first login, as I've sometimes seen Chrome not completely initialize an account profile. So, if you're using Chrome, try another browser. My other solution I consider superstition, but it has worked so many times that I still use it: I just remove the SharePoint Online and Office Online licenses from the account, save the change and wait a minute, then add those two licenses back. The next time the person logs in, it usually works.1.9KViews0likes2CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi ssquires, Thanks very much for this follow-up. Based on your response, I spent several hours last week re-examining my configuration. I do use term-driven pages.I think the issue was that, while I had an entry for Level 0 (site collection home), I did not have a URL specifically configured for it. It was never required for the link to work in classic managed navigation. Once I added that URL and let things sit overnight, all the child links fell into place. So that is a huge win for us, and will enable us to start to use modern libraries in our existing site collections. Also, the fact that the text in the drop-down and fly-out items is no longer truncated is a great improvement. I've noticed three other differences in managed navigation as deployed in modern libraries: 1. If a level 2 (drop-down) item does not have a level 3 (fly-out) child, the URL "preview" appears as expected in the lower left corner of the browser when you hover over the level 2 item. If it does have a level 3 (fly-out) child, no URL "preview" appears when you hover over it. All level 0, 1, and 3 "previews" appear as expected. The links function correctly, but it would be nice if the level 2 previews appeared consistently, as they do in classic mode. 2. The response in the appearance of the navigation drop-downs and fly-outs is noticeably slower than in classic mode. Not bad, but not the lightning-fast feel we're used to. 3. If one hovers over a level 1 (global nav) item to display the level 2 drop-down and then does not click on one of the level 2 or level 3 items but simply moves the cursor away from the navigation area, the drop-down (and, if chosen, the fly-out) menu remains open until one clicks elsewhere on the page. In classic mode, the drop-downs disappear immediately when the cursor is no longer hovering over the navigation item. This need for an extra click contributes to the feeling that the response is a bit more cumbersome than in classic navigation. Nonetheless, the fact that all levels of managed navigation now appear to lead to the correct URLs is a great breakthrough for us, and I very much appreciate your sticking with this! My next task is to get this to work in classic publishing sites that don't use managed navigation. Right now, when viewed from a modern library the drop-downs display all the contents of the level 1 sites as well as the links to the level 2 sites, which is not the desired behavior. Is that your experience, as well, or am I doing something wrong? Thanks again for all your help! Richard2.5KViews1like6CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
Hi ssquires - I'm just wondering what the time line might be for supporting the use of Modern Document Libraries and Lists in long-existing classic sites that utilize the Publishing feature and Managed Navigation for the Global Navigation (structured for the Quick Launch). Here's what I see right now: Consider Level 0 as the top of the site collection, Level 1 as the link that appears across the top in the Global Navigation, Level 2 as the drop-down, and Level 3 as the fly-out to the right. In a Modern Document Library view of the navigation: * Level 0 appears in the Global Nav but does nothing when you click on it * Level 1 links work * Level 2 links work * Level 3 links are broken, as they omit Level 1 from the URL. I.e., the URL becomes .../sites/0/2/3 (no "1"). It seems we are so close. Is there hope? Also, any hope for being able to display the Quick Launch (structure navigation) in collapsed form by default? Thanks, Richard2.7KViews0likes8CommentsRe: New Communication Sites
I've often thought about creating Groups and Teams under /teams rather than /sites, as a means of avoiding any potential URL conflicts, but I've been hesitant to make that split. Is doing so a fairly common practice, or have most people been like me and kept everything under /sites?5.9KViews0likes3CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
PhilineVon, I agree completely -- menu item truncation and and the considerably slower interaction time with the dropdowns and flyouts make the current Managed navigation experience in Modern mode considerably less useful and pleasant than in Classic mode. If we can regain the ability to utilize CSS to customize the appearance of the dropdowns/flyouts, we would, of course, have control over this. Short of that, at least eliminating truncation would be preferable. One of the main reasons to go to Managed navigation in large sites is the lightning fast display and interaction with the menus in the Global navigation. Since links to third levels don't yet work, I'm sure this is a work in progress.8KViews1like0CommentsRe: Editing Site Columns on Sub-Sites Doesn't modify the parent Site Column
If you are concerned specifically about Choice columns, you might consider using a site column of type Lookup, instead. Place the lookup target list of choices at the top level and don't allow sub-site admins write access to it.5.5KViews0likes3CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi ssquires, Thanks for your response and continued efforts to resolve these issues! One note: We also have Publishing sites using Structured navigation in global, with the same concept we use in our sites with Managed navigation. In looking at those sites, we see that Structured navigation also supports three levels, just the same as Managed Navigation. All that's required is that you check the box to Show Subsites in the navigation in the Level 2 site. Then you see the flyouts just the same as you have in Managed navigation. The picture below is such a site (Classic, Publishing, Structured Global). It seems to be just the Publishing feature itself that enables the third level, which is what makes the feature so valuable! Thanks, Richard18KViews0likes4CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi ssquires - Thanks for the reply. As you'll see in the description and pictures in my post on 4-Apr-2017, the site I'm working on is a Classic SharePoint site with publishing turn on for the site collection and the top level site, using Managed navigation for global and Structured navigation for the Quick Launch. It is not a Modern site, but I did create a Modern page and I set the view for the document libraries to show the Modern view to see how the navigation would appear on those pages. On other pages the navigation appears as it always has. When I'm on a modern page or a document library with a modern view, the navigation loses the flyouts (labeled level 3 in my screenshots) and does not follow the simple alternate CSS file I use simply to make each entry wider, put an outline around each entry, and add a highlight color when you mouse over an entry. The links (which omitted the "/sites/synctest/" part of each link in my earlier description) are now correct, so that's an improvement! But the existing dropdowns have no outline or mouse-over highlight color, so they're very hard to see, and the flyout level is missing. So my question is, is there work still going on that will address these issues, or is the current state the intended end state? My goal is primarily to be able to turn on the modern views for document libraries and lists in existing Classic SharePoint sites, but I can't afford to lose the functionality of our current navigation. Thanks very much, Richard19KViews0likes7CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
Hi ssquires - As far as I can see, neither structured nor managed navigation work in modern sites when the Publishing site collection feature is turned on. Is your group continuing work in this area to resolve these issues, or is this now considered the end state? Thanks, Richard19KViews1like9CommentsRe: Cannot Release Lock on SharePoint Online File
I've seen a few reports of something that sounds like this this in our tenant this week, mostly from Mac users. The error message appears in the MS Upload center when the person is trying to save a file they've been editeing. It says "The file ... is locked for shared use by <the same user> [membership]. The files are not large, e.g., a 45 KB Word doc. Haven't found a cure, yet. Richard546KViews3likes29CommentsRe: UPDATE: Support for Structured/Managed Navigation enabled on Modern Pages in Classic Team Sites
ssquires Perhaps it's just me, but I still see the same problems with Global navigation (Publishing turned on, using Managed Navigation (term set under the Site Collection tree), with a simple custom CSS to outline the drop-down boxes and shade them light blue on hover-over) that I've seen in the past when viewed from a Modern Document Library. It works fine when viewed from a classic page. Viewed from classic (home page of "Sync Client Test Site" site collection): Seen from a Modern Document Library: In the Modern view, there are no Level 3 flyouts, no observation of the custom CSS, and all the underlying links are wrong: they all omit the "/sites/synctest/" portion of the URL (i.e., the portion that specifies the site collection home). The only link that works is the default icon that takes you to the Home of the site. In the classic view, all the links work as expected. If I look at /sites/synctest/_layouts/15/topnav.aspx, there is only one link there, "Home", and it links to "/sites/synctest". Surely we're not supposed to have to edit that page on every site we've ever created to rebuild our navigation? Here's what my term store entry looks like: Any ideas? Thanks! Richard22KViews0likes0CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
People always have the simple option of right-clicking and opening a link in a new tab whenever they want. I would want to see the same default behavior as we see today in classic sites: any link in the global navigation should open in the same tab. Otherwise people will have the same maddening experience we see in O365 Groups, where navigating back and forth between the various functional parts of the Group ends up in a screen full of duplicate tabs. This behavior (opening in same tab) should be observed when just the Publishing feature is turned on and also when Publishing is turned on *and* Managed Navigation is in use. (I use Managed Navigation in the global nav, and structured navigation in the local nav.) If, in addition, you want to specify an option we can set to force opening in a new tab for a specific link, that would be fine; but the default should be as it is today - open in same tab for all links. It's easy for anyone to override and open in a new tab whenever they want, but there's no way for a person to override and open a link in the same tab. Richard Also, I have every site use the same global nav as the parent, so every site shows the same global nav as the top of the site collection.5.9KViews2likes3CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
ssquires- I've since found more problems with the managed navigation in Global. While the navigation looks fairly normal (except for the fact that the final level of navigation, the flyouts to the right, are missing), all the links drop "/sites/SiteCollectionName/" from the URL behind them, so none work. Also, for the links displayed across the top, I have to double click on them to go to the link (which, of course, has the wrong URL). The links in the drop-downs require only a single click, but, like the others, are missing the "/sites/SiteCollectionName/" part in the middle of the URL. This is a normal tenant - nothing in first release. All using IE 11. Finallly, in classic mode, hovering over any of the links shows the URL at the bottom left of the browser. In modern mode, the URLs are not shown.16KViews1like2CommentsRe: Structured Navigation (Publishing) not supported on "Modern" Sites/Pages/Lists/Libraries
I use managed navigation for Global in my production tenant. When I switch a single document library into Modern mode I am now correctly seeing the first level of drop-downs from each of the top level items, but not the second (normally displayed as fly-outs to the right of the drop-down items). Also, I have a very simple Alternate CSS that makes the width of the drop-downs a bit wider, adds a separation line between each drop-down item, and highlights in blue the drop-down item as you mouse over it - none of those effects are displayed when I put the document library into Modern mode. The drop-down items are highlighted in gray when I roll over them. Still, it is considerable progress!17KViews0likes5Comments
Recent Blog Articles
No content to show