Adds limit to post recursion when iterating through nested WordPress Posts#3
Open
andrew-boyd wants to merge 1 commit into
Open
Adds limit to post recursion when iterating through nested WordPress Posts#3andrew-boyd wants to merge 1 commit into
andrew-boyd wants to merge 1 commit into
Conversation
|
Please Merge. |
|
I need this |
|
Fix not working with type "Clone fields" |
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
4 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.
Our team ended up in a place where the recursion of this post could result in an infinite loop and take down the server. We're addressing it by storing the ID of WP_Post objects and then ensuring that we only iterate over them up to a set threshold (in our case, 1).