This article describes one way how to fix seemingly non-sensical “Access denied” errors, that you get when running Set-PnPAvailablePageLayouts. Problem While running the PnP cmdlet for enabling or selecting the available publishing page layouts for a web, you run into this, fairly generic error: Access denied. You do not have permission to perform this action or access this resource. PS C:\> Set-PnPAvailablePageLayouts -AllowAllPageLayouts Set-PnPAvailablePageLayouts : Access denied. You do not have permission to perform this action or access this resource. At line:1 char:1 + Set-PnPAvailablePageLayouts…Continue reading How to fix “Access denied” errors when running “Set-PnPAvailablePageLayouts”?
If your customers are anything like ours, some of them love the new modern library view, some will adjust and some just hate it and want to get as far away from it as possible. While embracing the new stuff is usually smart, there’s some value to sticking to what works as well. The Modern view is going to be the superior choice of the two (if it isn’t already!), but there are a multitude of reasons why one might want to revert to the…Continue reading How to revert Modern view back to Classic for SharePoint libraries using PowerShell
This issue seems to pop up bafflingly often, so I thought it’s finally time to document it for future generations. Granted, it mainly considers Classic SharePoint (which is very tightly built around Publishing features) – but Classic is going to be part of our lives for quite a while still, especially for those of us still primarily on SharePoint Server! While trying to provision subsites to your SharePoint Publishing intranet you encounter either a generic “Access Denied” -error, or any error with 0x80070005 as the underlying error…Continue reading Subsite creation in SharePoint fails with error 0x80070005 for any user (even global/farm admins!)
Every now and then, an API or a method call comes along, that you need to be very careful with. “Microsoft.SharePoint.Client.Web.AddSupportedUILanguage()” seems to be one of them. In this post, I’ll try and document my findings and workarounds for said method! Issues and solutions Posts Related to “Problematic behavior of web.AddSupportedUILanguage(int lcid) in SharePoint 2013 and 2016”:Frequently Asked Robot Lawn Mower QuestionsSharePoint Home, Hub, Sites, Start… What?SharePoint Localization – a (somewhat) comprehensive how-to!
SharePoint List Alerts. That magnificent functionality in SharePoint, that let’s you get a heads-up anytime someone touches your precious documents (so you can go and revert the changes), or changes files in Style Library (so you can go and remove that pink custom CSS they tried to add). Very useful for a lot of scenarios! The functionality is ancient, quite cumbersome and CERTAINLY not pretty, but it’s straightforward and quite reliable. On SharePoint Online, the notifications/alerts seem to work automatically, with no configuration whatsoever, and…Continue reading Subscribe to changes on a SharePoint list
Imagine this: you’re using a good old SharePoint blog site, and have a bunch of categories in use. That’s nice and easy – SharePoint offers the categorization functionality natively, and it works decently. Problems arise when you have a lot of categories, though – not all of them will be shown. Even if you tweak the web part to show more items on a page, this isn’t reflected on the whole blog site! This article explains how to fix this in a couple of simple…Continue reading How to show more than 30 categories on Classic SharePoint blog/news sites?
Twitter embed has a stupid, built-in failure condition: if the User Agent contains IE10 or older, the embed script will not load. This causes SharePoint embeds to fail. This post describes how to fix that.
This article describes an interesting feature of Multilingual User Interface in Classic SharePoint. So, in short, I encountered another, very interesting feature of Classic SharePoint Publishing sites, where multiple display languages were in use. When changing the web part title on a web part on a Classic SharePoint page, it seems like SharePoint saves the changes for you. In reality, only some users see the changes. So, in short: Some other users, on some devices, see the old title, whereas some see the new one.…Continue reading How to resolve Webpart title changes not reflected to some users?