Add legacy media file allowed content type for migrated field #280
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix: Add legacy media file allowed content type for migrated field
Fix: Add legacy media file allowed content type for migrated field - improvements
Chore: Remove GUID uppercase conversion
tkrch
approved these changes
Oct 29, 2024
This was referenced Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix: Add legacy media file allowed content type for migrated field
Motivation
Fix for reported missing referenced content type in migrated content type field
Checklist
How to test
Migrate Kentico11 to latest version of Kentico Xperience with migrator tool
Run xperience application.
Open admininstration panel
Go to Confiiguration/Content types page
Open any "Pages" content type
Locate any "Content items" field, open its configuration
Allowed content type must be filled