Skip to content
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

Latest Posts block: remove columns-x class for list view #4017

Closed
wants to merge 134 commits into from

Conversation

Soean
Copy link
Member

@Soean Soean commented Dec 14, 2017

Description

This PR removes the columns-x class for list view in the Latest Posts block. This class is only necessary for grid view.
Fixes #4015

Joen Asmussen and others added 11 commits December 12, 2017 10:23
This is round 2 of #3801.

It mitigates/fixes #503 and fixes #2024.

What remains to be done in this branch is:

- Make sure the text is translatable, right now it's hardcoded to "Edit Post"
- Make sure the text is contextual (so it shows Edit Page, Edit CPT etc)
This just uses the stock WordPress objects.
Adds test cases to fully cover the REQUEST_POST_UPDATE_SUCCESS effect.
@@ -52,7 +52,7 @@ function gutenberg_render_block_core_latest_posts( $attributes ) {
$class .= ' is-grid';
}

if ( isset( $attributes['columns'] ) ) {
if ( isset( $attributes['columns'] ) && 'grid' === $attributes['layout'] ) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the surrounding code, it looks like this should check to make sure the layout key exists before checking its value.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove all isset() from this file, because the attributes were moved to the server in #2529
cc: @aduth

Copy link
Member

@aduth aduth Dec 15, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might still want the 'grid' === $attributes['layout'] check though since based on the behavior in the editor, it seems that columns are only relevant for the grid layout. Edit: Ah, that's the whole point of the PR I see 😅

youknowriad and others added 27 commits December 26, 2017 17:39
When there are no Reusable Blocks available to add, and the user selects
'Saved' in the Inserter, display a message instead of a completely blank
tab.
We were requesting all category fields while needing three of them, this change makes sure we request only the fields we need.
The mixins apply editor left/right position to the selector passed as argument. It allows to use position fixed with correct dimensions.
…dths lower than small breakpoint.

Used editor-left & editor-right mixins to correctly position notices.
This change removes duplicate code and solves a bug related with resizing to small screen expanding WordPress menu and then resizing back to big screen.
Add 'No saved blocks' message to Inserter
…o-api

Add ability to delete a Reusable Block to REST API
* Bump `node-sass` to latest 4.7.2 release

* Update `package-lock.json`
@Soean Soean closed this Dec 29, 2017
@Soean Soean deleted the update/latest-posts-list-columns branch December 29, 2017 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.