-
Notifications
You must be signed in to change notification settings - Fork 383
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
Always allow switching from Transitional to Native #2312
Comments
I think the opposite is true: Native ==> Transitional; but Transitional does not imply Native. |
I'm referring to the theme not to the site. If a theme is marked as being Related to this is #2314 and whether AMP can be disabled for a given page/template. If a theme is not
This is true at a site level when considering plugins. |
Here's a plugin which forces Native mode even for themes that declare themselves as Transitional ( |
Testing Instructions
And:
And:
|
* Always allow switching from Transitional to Native on sites that are defined with `add_theme_support('amp', ['paired' => true])`. Fixes #2312. * Restore suppression of validation error warnings appearing in Reader mode. Fixes #2311 * Add functionality for users to chose AMP + Stories, AMP-only, Stories-only. Fixes #2470 * Phase out “Native” terminology in favor of “AMP-first”. Fixes #2507.
If
add_theme_support('amp', [ 'paired' => true ])
is present, then a user should still be able to still switch from Transitional to Native via the AMP admin screen, and back from Native to Transitional. If a site works in Transitional mode then by definition it should work in Native mode. But ifpaired => false
(orpaired
is absent), then Native would be the only option, as the reverse is not true: if a theme only works in Native mode then it may be using AMP components in its templates (e.g.amp-sidebar
) without any non-AMP version also implemented.This will allow all Paired themes (e.g. Neve) to be also used in Native mode.
The text was updated successfully, but these errors were encountered: