[N/A] Fix bug when stdClass is passed into ACF renderCallback function #5
Conversation
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
nathan-schmidt-viget
approved these changes
Oct 21, 2025
ten1seven
approved these changes
Oct 21, 2025
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.
Summary
In more recent versions of ACF, sometimes an
stdClassobject type can be passed into therenderCallbackfunction for ACF blocks. This fixes a bug that prevents a fatal error from occurringstdClassis used.Issues
Testing Instructions
This issue was difficult to reproduce because the
stdClasstype variable only appears randomly for some blocks, but it's not easy to identify which or why.