-
-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Continued byline changes #1265
Continued byline changes #1265
Conversation
…ne classes to use that to determine whether to load published-date or updated-date
so is the behavior here that we show either the updated date OR the published date but not both? are we still doing the XX hours ago for posts published/updated in the last 24 hours? or just posts published in the past 24 hours? |
Here's what shows:
|
|
…y 'largo_modified_time' to the byline classes
lgtm, passing this to @rclations for a second set of eyes and then let's merge |
everything looks good to me! |
And the failing tests are the usual, so I'll merge this and deploy it to Rivard. |
Changes
largo_post_was_updated( $post )
ininc/conditionals.php
largo_post_was_updated
inLargo_Byline
and its inheritor classes to determine whether to show the published date or the updated dateis_single()
<time>
element, to match the published dateh5.top-time
time element from the single post template, and styles for itWhy
For #1259, continuing #1126.
For the Rivard Report.