Release 2.0.2 · ampproject/amp-wp

This release follows up on 2.0.0 and 2.0.1, fixing a few issues reported in that release as well as making a few other enhancements.

For the full list of issues and pull requests in this release, please see the 2.0.2 milestone, with 9 closed issues and 20 merged pull requests. See full diff of changes.

Changelog

Identify the theme or plugin responsible for calling amp_is_request() (is_amp_endpoint()) or amp_is_available() prematurely when the _doing_it_wrong() usage notice is raised. Also identify the theme/plugin that is responsible for causing a fatal error during post-processing to display on the resulting error page. #4602, #5289
Ensure amp_is_available() returns false when accessing Database Repair screen. #5362
Ensure the GitHub link to the source is formed correctly in generated documentation. #5359
Remove instances of @return annotation in hook documentation. #5344

Cache error index counts and URL count in “At a Glance” dashboard widget, eliminating the need to run additional SQL queries with each admin page load. #5271, #5343
Only add_admin_menu_new_invalid_url_count when post type is show_in_menu. #5336

Gracefully handle sanitization of validation errors caused by use of i-amphtml-* in CSS selectors or class attributes. Instead of removing the entire style[amp-custom] or the entire class attribute, now just the invalid CSS selector or class name will be removed. #771, #5356
Update AMP validator spec to 2008290323001 and improve i-amphtml-* sanitization. #5356
Validate and sanitize image candidates in srcset attributes. This prevents the sanitizer from leaking an error: “Multiple image candidates with the same width or pixel density found in attribute ‘srcset’ in tag ‘amp-img’.” #5358, #5366
Gather required script components even for kept invalid markup. #5388
Prevent fatal error during post-processing from being masked by a notice. Call error_get_last() prior to calling sanitizers. #5375
Fix parsing of turn unit in CSS. #4604, #5392
Update button text used in the locked post dialog when editing a validated URL post. #5354

Avoid showing blank settings drawer for Plugin Suppression when no other suppressible plugins are active. Show message instead. #5310, #5349
Fix ability to complete onboarding when Twenty Twenty is chosen as Reader Mode on a Twenty Twenty site. Override Reader mode selection and re-set page index before reaching done screen. #5351, #5361
Harden presentation of available Reader themes. Ensure get_default_reader_themes returns an array and sets the array as a class attribute, and handle failed themes_api in UI. #5367, #5368

Prevent showing Gutenberg's new Widget Blocks section in Customizer for a Reader theme, since widgets in general are not currently supported in Reader mode. #5322, #5338
Ensure robots meta tag is added to AMP legacy template when search engines are discouraged. #5339
Fix displaying relative publish date/time in legacy AMP post template when timezine is not UTC. Ensure post_publish_timestamp in AMP_Post_Template is UTC for human_time_diff(). #5335

Allow test in Test_AMP_Core_Block_Handler to run now that WordPress/gutenberg#25026 has been merged. #5347
Fix test_add_block_source_comments with latest_posts dataset when Gutenberg installed from source. #5346

Thanks to the many contributors who made this release possible through work on development, design, testing, project management, and more:

Alain Schlesser (schlessera), Alberto Medina (amedina), James Osborne (jamesozzie), John Watkins (johnwatkins0), Joshua Wold (jwold), Kasper Myram (kmyram), Pascal Birchler (swissspidy), Pierre Gordon (pierlon), Renee Johnson (ernee), Weston Ruter (westonruter)

You can also install the amp.zip build linked below by uploading it in the WordPress admin.

To install as a Git submodule, consider 2.0.2-built.