Use return_format on ACFs within the media site. #52
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
The issue is that the media site also needs to respect the Advanced Custom Fields' return format. In the code we ask it to kindly skip the formatting of the ACF if we are in the media site. The fix is to allow the ACF to be formatted, independent of which site or context the filter is run from.
the field value if accessed via the admin panel. (e.g. is_admin() yields true).
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.
This commit will fix issue #51.
The issue is that the media site also needs to respect the
Advanced Custom Fields' return format. In the code we ask it to
kindly skip the formatting of the ACF if we are in the media site.
The fix is to allow the ACF to be formatted, independent of which
site or context the filter is run from.