fix: avoid conflict in the enqueing script with conditional display#3689
Open
fix: avoid conflict in the enqueing script with conditional display#3689
Conversation
📝 WalkthroughWalkthroughModified the block script enqueue logic in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🤖 Pull request artifacts
|
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.
fixes #3688
fixes #3693
Issue: When the first carousel (or any other block with frontend script) in the post is removed using
Conditional Display, its frontend script will not be enqueued.The conditional display feature removes the block content of the blocks to avoid rendering the block. If there's no block content for that block, the
wp_enqueue_scriptdoes not proceed (tested). However, the$scripts_loadedtracker, prior to this PR, attempts to enqueue the script, fails silently, but still records that the script is loaded. This will omit the succeeding attempts to enqueue the script, even though they are valid with proper block content.This PR makes the
Conditional Displayrun first to avoid race condition (in the premium PR), and check for empty block content before enqueueing the script since it might be removed withConditional Display.Summary by CodeRabbit