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
Add support for allowing a site subset to be native AMP #1235
Commits on Jun 27, 2018
Commits on Jun 28, 2018
Commits on Jun 29, 2018
Commits on Jun 30, 2018
-
Don't show post enable/disable if template is not available
Fix up some tests Address CR feedback [ci skip]
Commits on Jul 1, 2018
-
Let template_availability return supported when no templates match bu…
…t all supported * Fix remaining unit tests * Mock external HTTP requests [ci skip]
-
Let theme support args define templates_supported
* Make sure admin screen shows proper options when optional amp theme support has been disabled. * Add get_theme_support_args method.
-
Persist user selection even when checkbox disabled
* De-duplicate logic
-
Add tests for read_theme_support, is_support_added_via_option, get_th…
…eme_support_args Store version with options to keep track of format
Commits on Jul 2, 2018
-
Improve testing of finish_init; add test stubs
* Clean up covers tags * Remove unnecessary is_template_support_required
-
Elimiante Other/unrecognized template option since indistinguishable …
…from is_home * Devs should use filter to add support for custom templates * When a custom template is added via amp_supportable_templates filter then is_home will be discarded if there is another match
-
Restore the availability of AMP components in non-AMP documents in na…
…tive sites Revert "Remove dirty AMP support; rename Disabled to Classic" This reverts most of commit 5bae33e.
-
-
-
-
Restore available_callback but mark as deprecated
Use _doing_it_wrong() instead of trigger_error()
-
-
Fix initialization of paried mode and Customizer, and fix support opt…
…ions on admin screen