Recycle Bin and Site Content Hidden for Site Members and Site Visitors
I have a requirement that the Recycle bin and Site Contents should not be be hidden from the Site Members and Site Visitors. Please how can I achieve this because the Server Infrastructure activation is not working for me. Any workarounds? Please helpRecycle Bin and Site Content Hidden for Site Members and Site Visitors
I posted this before but made a mistake with my write up, so I am reposting. I have a requirement that the Recycle bin and Site Contents should be be hidden from the Site Members and Site Visitors. Please how can I achieve this because the Server Infrastructure activation is not working for me. Any workarounds? Please help
Accessing External Sharepoint Site
I am able to access internal Sharepoints within my company and have up until now been able to access Sharepoints outside the company. When I now try to access an external Sharepoint, I get the following message on the external company's landing page. "Your account has been locked. Contact your support person to unlock it, then try again...." The external company states they have not made changes any access protocols. Likewise, my company says nothing has changed with respect to the rules/ability to access external Sharepoints. Someone indicated that the Microsoft “federation” settings/setup of the two companies may (now) be incompatible. Has anyone encountered this issue?SharePoint List Accessibility Issues
I have team members that go around with iPads so that they can document issues at our sites within a Microsoft List. However recently there has been an issue where the save button just cant be reached anymore when using the web version. We tried using the SharePoint app, however that just results in the picture fields becoming read only, am i doing something wrong here? Is the only way to solve this through customized forms in Power Apps? Because that also just turns all my fields into custom data fields.New Sharepoint Quick Access - Want "Sites" back
I want the Sites back on my quick access menu - I don't want to have to go through "Discover" it just adds an obnoxious extra step and I can get there clicking on the Sharepoint logo on the top left - having another button to take you to the hub is pointless. How do I get Sites back on the quick access?
404 error downloading file versions via CSOM (SharePoint 2013 On-Prem)
I need to download historical versions of a document from a SharePoint 2013 On Premises document library using a C# console application, so I can migrate them chronologically to SharePoint Online along with their column properties. While downloading the current latest version works perfectly, downloading older historical versions always fails. Standard CSOM methods fail because ListItem.Versions does not exist in the SharePoint 2013 v15 SDK. Reverting to direct HTTP endpoints consistently throws an error. Here is the exact exception message I receive: System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found). Below is the minimal reproducible code example demonstrating how the connection is initialized, how properties are loaded, and where the download fails on historical versions: using System; using System.IO; using System.Net.Http; using Microsoft.SharePoint.Client; using SP = Microsoft.SharePoint.Client; class Program { static void Main() { string siteUrl = "https://example.com"; using (ClientContext sourceCtx = new ClientContext(siteUrl)) { sourceCtx.Credentials = System.Net.CredentialCache.DefaultCredentials; List sourceList = sourceCtx.Web.Lists.GetByTitle("MyLibrary"); CamlQuery query = CamlQuery.CreateAllItemsQuery(); ListItemCollection items = sourceList.GetItems(query); sourceCtx.Load(items, ic => ic.Include( item => item.Id, item => item.File, item => item.File.Versions, item => item.File.ServerRelativeUrl )); sourceCtx.ExecuteQuery(); foreach (ListItem item in items) { if (item.File == null || !item.File.Exists) continue; foreach (FileVersion ver in item.File.Versions) { string absoluteVersionUrl = siteUrl.TrimEnd('/') + "/" + ver.Url.TrimStart('/'); using (var handler = new HttpClientHandler { Credentials = sourceCtx.Credentials }) using (var client = new HttpClient(handler)) { client.DefaultRequestHeaders.Add("X-FORMS_BASED_AUTH_ACCEPTED", "f"); client.DefaultRequestHeaders.Add("User-Agent", "Mozilla/5.0"); // CRITICAL FAILURE HERE: Always throws 404 Not Found HttpResponseMessage response = client.GetAsync(absoluteVersionUrl).Result; response.EnsureSuccessStatusCode(); using (Stream fileStream = response.Content.ReadAsStreamAsync().Result) { // Upload logic to SPO goes here } } } } } } The version URL returned inside the property matches the following virtual folder layout format: _vti_history/512/Folder/Doc.docx My specific environment queries are: Why does navigating to the absolute history folder URL over an authenticated HttpClient trigger a 404 Not Found error in SharePoint 2013 on premises, even though the path token is extracted directly from the version url metadata property? Is there an alternative legacy REST endpoint routing structure or an alternative file stream extraction method available in the SharePoint 2013 (v15) SDK that allows an external client application to fetch older version binaries successfully?SharePoint Permissions Management
Over the last 3 years of managing permissions across a suite of sites, I have uncovered more new issues with the way SharePoint permissioning is designed at every turn. A few examples, before the question: If I "Share" a file or folder somewhere on the site (breaking permissions inheritance), it is very inconvenient to find it again. If I "copy link" in this one particular way, permissions inheritance is broken. When looking at site-level permissions, I see site-level permissions groups, but there could be hundreds of other users who have been added to my site(s) without my knowing. If I want to reset permissions in an area (set of folders or library), I have to do it file-by-file or folder-by folder. If I want to get an excel snapshot of - anything really - IT has to pull it and it takes a couple days. Not to mention the permissions interface is incredibly clunky. All-in-all, there seem to be a million ways to break permissions inheritance, creating an access tracking and security nightmare. AND there's no easy way to truly see and understand who has access to what or what is broken, without spending hours with IT to pull a bunch of narrow-visibility reports. So my question is: what is the best way to navigate full permissions visibility? Am I doing something wrong? Is anyone else experiencing these issues? We have resorted to having a very strict "no outsides besides a few exceptions" policy and only managing permissions at the site-level, which really hampers on the collaboration benefits that SharePoint is trying to enable. It is also very administratively intensive. One of the benefits to SharePoint is that users don't really need to understand how it works to use it, but that's becoming less and less true with the increasing lack of security we feel in the platform.
