Fix replicators not working from Runway resource blueprints#208
Open
Jade-GG wants to merge 1 commit into
Open
Conversation
kevinmeijer97
approved these changes
Jul 6, 2026
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
2 participants
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.
ref: AN-432
Since what I assume would be the Statamic 6 upgrade, the
vendor.runwayhint path is used for the blueprint token in Replicators and Bards. This path does not get recognized because of the way we have set up our Runway integration.This means that instead of using the correct path
runway::categoryusing the runway namespace, it will spit out the rawvendor.runway.categoryand look for a blueprint with that exact name.This line gives Statamic enough information to not do this, and look for the blueprint in the proper location.