Add term class to largo_top_term() output, prevent largo_category_and_tags() from using wrong post in fallback scenario. #1648
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:
largo_top_term()
from callinglargo_category_and_tags()
when the post ID passed tolargo_top_term()
does not matchget_the_ID
's post ID, because there is presently no way to pass that ID tolargo_category_and_tags()
.taxonomy-slug
output as class onlargo_top_term()
for the top term, and inlargo_category_and_tags()
to support that output in a fallback case.largo_top_term()
, and changed tolargo_maybe_top_term()
while I was in there. This means thatlargo_top_term()
will have the specified post ID in that zone, and in combination with thelargo_category_and_tags()
change above, if there's no top term set on a post, there'll be no emptyh5
element there.