-
Notifications
You must be signed in to change notification settings - Fork 384
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
Highlight AMP-compatible themes and plugins in admin #6597
Highlight AMP-compatible themes and plugins in admin #6597
Conversation
Plugin builds for 49b37fa are ready 🛎️!
|
This pull request introduces 1 alert when merging 0cc9223 into 3f0146e - view on LGTM.com new alerts:
|
@dhaval-parekh I ran into an issue trying to test this. Just to clarify, does this also work when searching plugins and themes? |
This pull request introduces 1 alert when merging 2df393c into deba08a - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging af2799a into f819294 - view on LGTM.com new alerts:
|
@jwold I think previously it was a bug and not showing. PX message after serach. But it's fixed now. |
Regarding #6597 (comment):
OK, I think I see. So the debouncing must be at least 1001 milliseconds because before that there is no guarantee that I think what may be required is to use |
* Override theme view. | ||
*/ | ||
overrideViews() { | ||
wp.themes.view.Theme = ampViewTheme; |
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.
Something we may need to look out for here: what if another plugin is also doing a similar thing? Will their overrides get lost? I suppose not if they are also extending wp.themes.view.Theme
because if they do so then they would be extending our extension, or vice-versa. Still, something to look out for.
$response->themes[ $i ] = (object) $theme; | ||
} | ||
} else { | ||
$response->themes = $themes; |
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 doesn't seem to ever be called.
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.
Yes, We can remove that. But need to make sure the function only serve when $action is 'query_themes'.
I have updated it in the new PR #6681
*/ | ||
public function filter_plugins_table_api_args() { | ||
|
||
$per_page = 100; // @todo There are currently 56 plugins, so this will show all. This is done because pagination is not working. |
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.
@dhaval-parekh Please look into pagination of the AMP-compatible plugins list in another PR.
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.
Please have a look at this PR #6681
I have addressed the pagination issue in this PR.
Summary
Fixes #2313
AMP-GH-Issue-2313.mov
Checklist