Add warning output if WP_DEBUG || LARGO_DEBUG about the third parameter of largo_byline being required #1561
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
…byline() is called without specifying a post or post ID.
…er of largo_byline being required Also, fix a number of partials and templates that were not in compliance with the new regime. Part of #1517
6 tasks
|
Bugfixes in #1574 |
27 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.
Changes
Why
Because when you call largo_byline() without a post specified, sometimes the global
$postand the post you're displaying stuff for don't match. This causes problems.The first part of #1517: the plan to eventually deprecate calling largo_byline without specifiying a post.