-
Notifications
You must be signed in to change notification settings - Fork 87
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
Lesson Plans: Landing page, archive and single page layouts #867
Conversation
This landing page looks great! Excellent work and thanks for contributing @danhthong! I will need someone from the dev team to do a code review - perhaps @adamwoodnz? - but the layout works well from my side! One note is that this will not be set as the home page of the site, but will need to live at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Page needs to exist at /lesson-plans
while still maintaining the filtered lesson plan archive pages.
@hlashbrooke I have updated as your requested to keep current url by d8783ab. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works just like I expected and I'm very happy with this! Thanks for updating the PR @danhthong!
This will still need a code review before we can merge, so we need to wait on that.
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_section-heading.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_section-heading.scss
Outdated
Show resolved
Hide resolved
This I can see it's existing though. Do we want to keep it @courtneyr-dev @hlashbrooke ? |
wp-content/themes/pub/wporg-learn-2020/css/components/_card.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_section-heading.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_section-plan-desciption.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/css/components/_page-lesson-plan.scss
Outdated
Show resolved
Hide resolved
wp-content/themes/pub/wporg-learn-2020/template-parts/content-single.php
Outdated
Show resolved
Hide resolved
c639d49
to
4d337c9
Compare
@adamwoodnz All done. Thank you a lot! |
update_term_meta( | ||
$term_id, | ||
'dashicon-class', | ||
sanitize_text_field( $_POST['dashicon-class'] ) // phpcs:ignore WordPress.Security.NonceVerification.Missing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@iandunn any concerns about these ignores?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically they should have something like
if ( /* is inserting new term */ ) {
check_admin_referer( 'add-tag', '_wpnonce_add-tag' );
} else {
check_admin_referer( 'update-tag_' . $term_id );
}
...but in practice that should be covered by the nonce that already exists in edit-tags.php
Switching to that would be ideal IMO, but not a blocker
I'm seeing some odd styling on the Learn homepage cards They appear to be missing this padding rule Same for you @danhthong ? |
IIRC that padding will be off for you because it is actually coming from the Customiser on the live Learn site. I will confess that I added it (along with some other custom CSS) when I wasn't able to contribute code properly but needed the styling to be done. Now that I think of it, I'll create a new issue for moving any CSS from the Customiser into the actual theme files. UPDATE: Added an issue here: #937 |
Adding this locally fixed it, thanks @hlashbrooke I'll approve this now, and merge and deploy once I get the all clear from @iandunn. We'll need to select the categories and audiences for the landing page cards and choose dashicons for them after deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉
Thanks for all the hard work here @danhthong and @adamwoodnz - this is going be great to have live! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry @danhthong but I've found another issue with the sticky field. I don't seem to be able to un-sticky a category:
It's the same for Audiences.
@adamwoodnz I updated for last issue and add check to skip phpcs ignores. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me!
This PR for #153
Steps to update Lesson Plans landing page.