V14: MediaPicker/MNTP - Changed StartNodeId from a Udi to Guid#16042
Merged
V14: MediaPicker/MNTP - Changed StartNodeId from a Udi to Guid#16042
StartNodeId from a Udi to Guid#16042Conversation
4 tasks
kjac
approved these changes
Apr 16, 2024
Contributor
kjac
left a comment
There was a problem hiding this comment.
Looks like an oversight indeed 👍 good stuff!
This file contains hidden or 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
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.
As discussed with @Migaroez, I suspect these were missed during the data type configuration migration work.
Strange thing is that the frontend (beta002) had been working with these fine until yesterday, when it started to throw errors about the MediaPicker and MNTP configurations, so I'm not sure if something else changed on the server-side, but correcting the object-type appears to fix this.