[ Navigation ] Fix dynamic rendering recursive function name typo #21078
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
draganescu
requested review from
ajitbohra,
jorgefilipecosta,
Soean and
talldan
as code owners
|
Size Change: 0 B Total Size: 857 kB ℹ️ View Unchanged
|
draganescu
deleted the
fix/navigation-block-function-name-typo-fatal-error
branch
12 tasks
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.
Description
Somehow I managed to botch master by merging #20076 which had the rendering function named wrong.
How has this been tested?
Tested locally. Before the change attempting to view a page or post containing a navigation menu resulted in:
Fatal error: Uncaught Error: Call to undefined function core_block_navigation_build_html()Types of changes
Bug fix.