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.
The Problem
We're running a filter on post body content that checks if the post starts with an image, and if that image matches the post's featured image, removes the content from the post display (to prevent duplicate displays of that featured image).
The issue is the method we're running that check. Currently, we're getting the source for the image in the post body, then running a very slow query to lookup that image's ID in the database. This type of query/logic cannot continue to exist for performance reasons.
The solution
Every image inserted by the media editor should have a
wp-image-##
class on it, where##
is the id of the media file. By pulling this ID out with regex, we can achieve the same effect, but avoid expensive queries.Potential Downsides
If the html for the image has been manipulated or inserted by hand so that it does not include the
wp-image-##
class, then this obviously won't work.