make reference tags parsing work with generated fields#18725
Closed
make reference tags parsing work with generated fields#18725
Conversation
Member
|
This ended up being just a bug in |
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.
Description
Adds the ability to parse generated fields in reference tags.
To test:
myTestand a value ofabcde<p>{{ craft.app.elements.parseRefs('{entry:194:myTest}') }}</p>(replace the number with the actual ID of the entry from the previous step)Before this change, the result would be the entry’s URL (if the section is configured with URIs) or an empty string (if configured without URIs).
With this change, you should see
abcde.Related issues
#18692