Solving “Tenant app deployment is only supported in the app catalog site. The current site is not the app catalog site.” error

Something went wrong in SharePoint

Got an error “Tenant app deployment is only supported in the app catalog site. The current site is not the app catalog site.”, even if the current site very much IS an app catalog site? There might be an easy fix!

Problem

Imagine this: you browse into your fresh SharePoint tenant, open the app catalog, click on an app, try to deploy it, and out comes this error.

Tenant app deployment is only supported in the app catalog site. The current site is not the app catalog site.

Yes, while trying to deploy an app from app catalog, you get an error that the current site is not the app catalog site. Frustrating!  Continue reading

Solving “Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic.” in SharePoint

SharePoint cat fixing them errors

This is one of the kind of weird issues that you don’t really run into in your own development environments, but that you more often run into when you actually have non-godlike permissions. Oh, the woes of trying to use SharePoint with anything less than farm/global administrator… 🙂 Anyway, in this post I’ll describe a couple of solutions to an error: “Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic”.

You might encounter this issue, when uploading pretty much any files in any SharePoint document library. Typically, I run into this when trying to update a file in a library (in my case, the only times I’ve ever seen this, have been the Style Library of a SharePoint site). You can apparently encounter it with any file type, in this example below, it happened with a JavaScript (.js) file.

Style Library throwing an error: "Sorry, your files couldn't be uploaded. The upload might be too large or the server might be experiencing high network traffic."

Style Library throws an error:
“Sorry, your files couldn’t be uploaded. The upload might be too large or the server might be experiencing high network traffic.”

Funnily enough, I usually encounter this issue with a following set-up:

  • On-premises SharePoint server (2013 or 2016 – occasionally also SharePoint Online, but that’s less typical!)
  • Small files (of 1-200kb)
  • The server has been experiencing very low network traffic.

The error really doesn’t seem to describe the issue at all – so what’s actually causing this?

Solution(s)

Quick googling didn’t give any actual reasons or fixes for the issue. A lot of people online seem to suggest changing your browser to something else from Internet Explorer… While it might not be a bad idea in itself, it does seem like a ridiculous fix – and also didn’t work for me 🙂

However, every single time so far, going through this checklist has helped me solve the issue and get rid of the error: Continue reading

SharePoint Localization – a (somewhat) comprehensive how-to!

Let me explain SharePoint

Localization – or showing users with different language preferences content in their preferred language – is not SharePoint’s strongest suite. It never was, and probably will never be, unless Microsoft perfects Machine Translation at some point. And even then it would probably require extra subscription, as Cognitive Services APIs are not available (above the peasant-tier) for free now either. In this article I’ll go through a few survival strategies for multilingual organizations – and I’ll try to expand the content as more options pop up!

Please note, that this article revolves mostly around Classic SharePoint. Microsoft’s current implementation of Modern SharePoint offers little-to-nothing for a controlled localization. It offers a curious way to use MUI to offer multilingual chrome with non-localized content, and that’s about it… But some of my tips work in Modern, too.

Different out-of-the-box localization features in SharePoint

So, what can SharePoint do out-of-the-box? There are a couple of features one can use – let’s go through them!

Continue reading

How to enable custom scripts for a SharePoint site collection?

This article explains how to enable custom scripts for any SharePoint site. Different instructions apply to SharePoint Online, and on-premises scenarios (SharePoint 2013, 2016 and probably 2019).

Different solutions resolve the issue for different target sites:

  • Modern SharePoint Team Sites (attached to Office Groups)
  • SharePoint MySites
  • Personal OneDrive sites
  • Any SharePoint site collection created based on self-service site creation
  • SharePoint Online tenant root site collection
  • Any Classic SharePoint site collection

Errors and causes

Most typically I run into this when trying to insert a script web part with custom JavaScript into a site, that has NoScript enabled. That’s annoying – since script webparts are incredibly useful! Continue reading

How to show more than 30 categories in SharePoint blog/news sites?

SharePoint doesn't work as intended

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 post article explains how to fix this.

Problem

For background info – the category listing is actually an XSLT list view web part. It’s not obvious just looking at it, but to change its view you’ll need to modify the list view it’s attached to.

With low numbers of categories, this works quite nicely.

SharePoint blog

SharePoint blog with categories

By default, however, SharePoint only shows 30 first (alphabetically ordered) of your categories. Weirdly enough, it doesn’t show any paging for them – and it doesn’t even indicate in any way, that it’s not showing all of the categories! This is a bit annoying, so luckily there’s a way to change this.

Continue reading

Opening a web part page in maintenance mode

SharePoint doesn't work as intended

Can’t access a web part page because of a broken web part? Yeah, that’s a classic issue – and it’s nicely ported into Modern world, too! In these cases, web part page maintenance mode comes in handy!

There’s a query parameter available for accessing it. For whatever reasons, it’s different for Classic and Modern mode, though. Why make things easy if you can make them dificult, right? 🙂  Continue reading

Hackathon win: Resolving Managed Metadata Madness

Won my first hackathon!

I won a hackathon! They had fun topics, it was a cool challenge, a well organized event, and had cool prizes. Since this is the first hackathon I ever took part in, I thought I’d post something about my experience and the solution(s) I figured out. Continue reading

How to show a Classic SharePoint page in dialog mode (without SharePoint’s full-blown chrome)

Let me explain SharePoint

Classic SharePoint actually has a very handy piece of functionality, using which you can hide most of the SharePoint chrome (like header and navigation), and hence make the page a lot more sleek. This is especially useful for showing the contents in a dialog window – which SharePoint also supports natively through JavaScript! This post describes how.

How to show any (classic) SharePoint page in dialog mode?

Pretty easy – it’s handled via a url parameter!  Continue reading

Using “DetectedLanguage” to return only localized results from SharePoint Search index

How to SharePoint?

Localization and targeting of content in multilingual SharePoint installations is always an issue. SharePoint offers a multitude of ways profile content based on user language (or other properties), but none of the solutions are fool proof. This post describes how to fetch only localized results from SharePoint Search index, which solves at least some of the issues.

Description 

SharePoint Search index can be used in quite a few different ways. Probably the most typical way is by searching on SharePoint, or using webparts like Content Search or Content Results. However, one can also build custom functionality, custom client-side liftups, webjobs, single-page applications, mobile applications and a ton of other things that fetch data from SharePoint search index. However, on multilingual tenants, results are, by default, not localized at all. That means, that typically everyone will get the highest-ranking results back, despite them being in the wrong language. And that’s one of the many, many ways to annoy your users!

Continue reading

Web part title changes not reflected to some users in multilingual SharePoint environment

SharePoint is not broken - it just does't work

I encountered another, interesting issue – this time in a SharePoint environment, 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. It’s a confusing situation and difficult to debug.

Why do web part titles get changed seemingly randomly?

Imagine this: You have a SharePoint environment, where you have multiple different languages set up. You also have users with multiple different workstation configurations – including multiple different languages. Different users, however, quite randomly see different revisions of web part titles in a very weird manner. This happens seemingly randomly even on new client devices, so no client-side caching is the reason.

This actually likely works as designed, it’s just kind of a confusing implementation. We’ve got Microsoft to blame for that, and their pretty bad documentation… SharePoint actually localizes (and hence saves) Web part titles per-language. This is just not very clearly explained (at all) when editing the page! Continue reading