Migration of the media libraries still failing when clicking "Migrate media libraries" button in media library admin

[purquhart]

Brief bug description
When a media library folder exists with spaces in it, the media migration to content hub throws an exception and fails.

Repro steps
Migrate a media library with spaces in the sub folder names:

• Go to the media library in the new Xperience by Kentico admin instance.
• Click the "Migrate media libraries" button in the media library.
• See the error in the event log.

Expected behavior
That the media libraries are successfully migrated when clicking the button.

Version
Xperience by Kentico version 31.0.0

Additional context
This bug is the same one as bug 515 that has been closed,

This is the error that is logged to the event log:

Source
MigrateMediaLibrariesToContentHubTask

Description
[null]
Message: 'name' is not a valid code name. (Parameter 'name')

Exception type: System.ArgumentException
Stack trace:
at CMS.ContentEngine.CreateContentFolderParameters..ctor(String displayName, String name)
at CMS.MediaLibrary.MediaFolderMigrationService.CreateFolder(String name, String displayName, Int32 parentFolderId, IContentFolderManager contentFolderManager, Nullable1 guid, CancellationToken cancellationToken) at CMS.MediaLibrary.MediaFolderMigrationService.RecursivelyEnsureSubfoldersStructure(MediaLibraryInfo mediaLibraryInfo, ContentFolderInfo parentFolder, String parentAssetFolderPath, IContentFolderManager contentFolderManager, IDictionary2 folderPaths, CancellationToken cancellationToken)
at CMS.MediaLibrary.MediaFolderMigrationService.RecursivelyEnsureSubfoldersStructure(MediaLibraryInfo mediaLibraryInfo, ContentFolderInfo parentFolder, String parentAssetFolderPath, IContentFolderManager contentFolderManager, IDictionary2 folderPaths, CancellationToken cancellationToken) at CMS.MediaLibrary.MediaFolderMigrationService.RecursivelyEnsureSubfoldersStructure(MediaLibraryInfo mediaLibraryInfo, ContentFolderInfo parentFolder, String parentAssetFolderPath, IContentFolderManager contentFolderManager, IDictionary2 folderPaths, CancellationToken cancellationToken)
at CMS.MediaLibrary.MediaFolderMigrationService.RecursivelyEnsureSubfoldersStructure(MediaLibraryInfo mediaLibraryInfo, ContentFolderInfo parentFolder, String parentAssetFolderPath, IContentFolderManager contentFolderManager, IDictionary2 folderPaths, CancellationToken cancellationToken) at CMS.MediaLibrary.MediaFolderMigrationService.EnsureSubfoldersStructure(Dictionary2 defaultFolders, IContentFolderManager contentFolderManager, CancellationToken cancellationToken)
at CMS.MediaLibrary.MediaFolderMigrationService.EnsureFolderStructure(Int32 userId, WorkspaceInfo workspace, CancellationToken cancellationToken)
at CMS.MediaLibrary.Internal.MigrateMediaLibrariesToContentHubTask.MigrateToContentHub(Int32 userId, CancellationToken cancellationToken)
at CMS.MediaLibrary.Internal.MigrateMediaLibrariesToContentHubTask.Execute(ScheduledTaskConfigurationInfo task, CancellationToken cancellationToken)

[radekzitta]

Hello @purquhart ,

You are right, the bug 515 was closed without any code changes. We modified the description of the LegacyPermissiveMediaLibrarySubfolders configuration key only.

Configuration

Allows media library subfolder names that don’t follow the current Xperience by Kentico naming rules. When set to true, skips validation requiring only alphanumeric characters, underscores, and hyphens, and allows names that may otherwise conflict with OS-reserved keywords (such as CON, PRN, AUX). This configuration should only be used when necessary (for example, when re-running migrations from older tool versions), as it may limit functionality like media library migration to the Content hub.

What was your configuration for the migration? If the LegacyPermissiveMediaLibrarySubfolders property was set to true, you must manually rename the folders in XbK and then try migration to Content Hub again.

[purquhart]

Hi @radekzitta I tried that configuration key on our current instance but that didn't seem to change anything - I think we might be talking about two different things though as that seems to be a migration tool configuration - this bug and 515 are referring to the migration behaviour that occurs when clicking the "Migrate media libraries" button in the website admin. If there is a better place for this to be submitted please let me know.

A bit of history: when we originally migrated the media library as part of upgrading to XbyK using the migration tool, we utilized the MigrateMediaToMediaLibrary flag as there wasn't a need to implement the media library as content item assets at that time. With media libraries being sunset now, we are looking to begin migration of our media libraries to content item assets along with refactoring the associated code - however, since everything went live long ago, simply re-migrating the media libraries to content item assets via the migration tool itself wouldn't be an option as we need to be able to utilize the functionality provided by the "Migrate media libraries" button in the admin section of the site in order to retain the existing metadata during the migration.

With that all in mind, it seems possible that the functionality which has been updated in the migration tool to handle the folders simply has not yet been ported into the migration functionality that occurs when clicking the "Migrate media libraries" with the admin section of the website.