Unable to select folder with Media Picker since upgrade to Umbraco 17.3

Good afternoon, I upgraded an Umbraco instance I have to 17.3, now I am unable to select a folder with a media picker that only allows folders to be selected.

I have another site running 17.2 and I am still able to do this.

Anyone else having this issue?

Hi Robert,

This is a known regression tracked as issue #21885 on GitHub. The fix was merged on March 3 and is included in the official 17.3.0 release notes, so it should be in the final build that shipped on April 2.

A couple of things worth checking:

  1. Confirm your exact version — make sure you’re on the final 17.3.0 and not an RC build, as the regression was present in the RC previews.
  2. Check your data type config — if your picker has allowedContentTypes set alongside the folder-only filter, there’s a known edge case where folders can still be rejected.

If you’re on the final 17.3.0 and still seeing the issue, it’s worth opening a GitHub issue with your data type configuration so the team can take a look.

/Bishal

1 Like

Thank you for the response, I can confirm that I am running the final 17.3.0 and not the RC

Server Troubleshooting:

  • Server OS: Microsoft Windows 10.0.14393
  • Server Framework: .NET 10.0.5
  • Default Language: en-US
  • Umbraco Version: 17.3.0
  • Current Culture: en-US
  • Current UI Culture: en-US
  • Current Webserver: IIS
  • Models Builder Mode: SourceCodeAuto
  • Runtime Mode: BackofficeDevelopment
  • Debug Mode: False
  • Database Provider: Microsoft.Data.SqlClient
  • Current Server Role: Single

Here are screen shots of my block & settings

Hi @rdjohnston-sjgov

You may want to post that in the GitHub issue tracker as it sounds like the same issue, even though it was supposedly fixed in 17.3. Does the same happen for you in a clean instance? What version did you upgrade from? Any further information could be helpful in diagnosing.

Justin

Can you please make absolutely sure you cleared your browser cache? That has caught me out so many times! :smiley:

Justin,

Thank you - I did and I believe the fix will be in the 17.3.1 release.

1 Like