1.5.3 Update Issues
-
We updated the AMP plugin last Thursday, and starting on Saturday we got AMP issues with google.
We are getting 4 different errors:
1: The tag ‘img’ should be replaced with an equivalent ‘amp-img’ tag.
2: A mandatory AMP HTML tag is missing from this document.
3: Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head.
4: External stylesheets not supported, except for whitelisted font providers. Use the document inline ‘style amp-custom’ tag instead.It’s currently only on 4 of our amp pages, however I noticed it’s an issue on all of them, google just hasn’t crawled them yet.
The page I need help with: [log in to see the link]
-
Yeah, I see that as well.
The post-processor isn’t running for some reason. Is anything showing up in the error log? Can you share your Site Health info?
No errors in apache.
Here’s a screen shot of the main health page:
then here’s the secondary info:
### wp-core ###version: 5.4
site_language: en_US
user_language: en_US
timezone: America/New_York
permalink: /articles/%postname%/
https_status: true
user_registration: 0
default_comment_status: open
multisite: false
user_count: 76
dotorg_communication: true### wp-paths-sizes ###
wordpress_size: 104.65 MB (109733655 bytes)
uploads_size: 431.75 MB (452724444 bytes)
themes_size: 56.44 MB (59184140 bytes)
plugins_size: 156.12 MB (163704625 bytes)
database_size: 71.00 MB (74453025 bytes)
total_size: 819.97 MB (859799889 bytes)### wp-dropins (1) ###
advanced-cache.php: true
### wp-active-theme ###
name: Mukam Child (mukam-child)
version: 2.1.5
author: Blicca Theme
author_website: https://themeforest.net/user/bliccathemes
parent_theme: Mukam Theme 2.1.9 (mukam)
theme_features: post-thumbnails, automatic-feed-links, post-formats, woocommerce, widgets, menus, editor-style### wp-parent-theme ###
name: Mukam Theme 2.1.9 (mukam)
version: 2.1.9
author: Blicca Theme
author_website: https://themeforest.net/user/bliccathemes### wp-themes-inactive (4) ###
: version: 1.0.1, author: AivahThemes
LifeCare: version: 1.0.2, author: AivahThemes
Twenty Nineteen: version: 1.4, author: the WordPress team (latest version: 1.5)
Twenty Twenty: version: 1.0, author: the WordPress team (latest version: 1.2)### wp-plugins-active (40) ###
a3 Lazy Load: version: 2.3.2, author: a3rev Software
Advanced Custom Fields: version: 5.8.9, author: Elliot Condon
AMP: version: 1.5.3, author: AMP Project Contributors
Autocomplete WooCommerce Orders: version: 1.2.2, author: Liam McArthur (latest version: 1.3.1)
BMI Calculator Widget: version: 1.3, author: Domain Superstar LLC
Contact Form 7: version: 5.1.7, author: Takayuki Miyoshi
Duplicate Page: version: 4.2, author: mndpsingh287
Enable Media Replace: version: 3.3.11, author: ShortPixel
Enhanced E-commerce for Woocommerce store: version: 2.3.4, author: Tatvic
GA Google Analytics: version: 20200325, author: Jeff Starr
Glue for Yoast SEO & AMP: version: 0.6, author: Joost de Valk
Holler Box: version: 1.5.2, author: Scott Bolinger
LayerSlider WP: version: 5.3.2, author: Kreatura Media
MailPoet 3 (New): version: 3.46.11, author: MailPoet
Multiple Post Thumbnails: version: 1.7, author: Chris Scott
Postman SMTP: version: 1.7.2, author: Jason Hendriks
Product Country Restrictions: version: 0.4.3, author: Bizilica
Regenerate Thumbnails: version: 3.1.3, author: Alex Mills (Viper007Bond)
Remove Yoast FAQ Block: version: 1.0, author: Agile
Sirv: version: 4.1.2, author: sirv.com
Text Attributes for WooCommerce: version: 1.0.1, author: Andrei Zobnin (latest version: 1.0.2)
Visual Form Builder: version: 3.0.1, author: Matthew Muro
What The File: version: 1.5.4, author: Never5
WooCommerce: version: , author: Automattic
WooCommerce Authorize.Net CIM Gateway: version: , author: SkyVerge
WooCommerce Custom Credentials CC Email: version: , author: Agil
WooCommerce Custom Credentials Email: version: , author: Agil
WooCommerce Custom Credentials RX Email: version: , author: Agil
WooCommerce Custom Product Addons (Free): version: , author: Acowebs
WooCommerce Email Test: version: , author: RaiserWeb
WooCommerce Max Quantity: version: , author: Isabel Castillo
WooCommerce Pretty Emails: version: , author: MB Création
WooCommerce Product Feed Manager: version: , author: RexTheme
WooSidebars: version: 1.4.5, author: WooCommerce
WPBakery Page Builder: version: 6.2.0, author: Michael M – WPBakery.com
WP Security Audit Log: version: 4.0.3, author: WP White Security
WP Sitemap Page: version: 1.6.2, author: Tony Archambeau
WP Super Cache: version: 1.7.1, author: Automattic
Yoast SEO: WooCommerce: version: 12.7, author: Team Yoast
Yoast SEO Premium: version: 13.5, author: Team Yoast### wp-plugins-inactive (3) ###
GDPR Cookie Consent Banner: version: 2.3.15, author: termly
Revolution Slider: version: 4.5.7, author: ThemePunch
Twitter Feeds: version: 1.6, author: Contributed### wp-media ###
image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1687
imagemagick_version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 https://www.imagemagick.org
imagick_limits:
imagick::RESOURCETYPE_AREA: 122 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 6144
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 4
gd_version: 2.2.5
ghostscript_version: 9.26### wp-server ###
server_architecture: Linux 4.15.0-1052-aws x86_64
httpd_software: Apache/2.4.29 (Ubuntu)
php_version: 7.1.32-1+ubuntu18.04.1+deb.sury.org+1 64bit
php_sapi: apache2handler
max_input_variables: 1000
time_limit: 30
memory_limit: 256M
max_input_time: 60
upload_max_size: 2M
php_post_max_size: 8M
curl_version: 7.58.0 OpenSSL/1.1.1d
suhosin: false
imagick_availability: true
htaccess_extra_rules: true### wp-database ###
extension: mysqli
server_version: 5.7.29-0ubuntu0.18.04.1
client_version: mysqlnd 5.0.12-dev – 20150407 – $Id: 38fea24f2847fa7519001be390c98ae0acafe387 $### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined### wp-filesystem ###
wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable### amp_wp ###
amp_mode_enabled: reader
amp_templates_enabled: post
amp_serve_all_templates: This option does not apply to Reader mode.
amp_css_transient_caching_disabled: false
amp_css_transient_caching_threshold: 5000 transients per day
amp_css_transient_caching_sampling_range: 14 days
amp_css_transient_caching_transient_count: 3
amp_css_transient_caching_time_series:
20200423: 3
20200424: 3
20200425: 3
20200426: 3
20200427: 3What about the PHP error log?
Also, try temporarily deactivating MailPoet to see if that fixes the issue. There may be a conflict in the PHP-CSS-Parser included in the AMP plugin and the MailPoet plugin.
No PHP errors. Also tried disabling MailPoet, didn’t work.
Please also try deactivating WP Super Cache in addition to deactivating MailPoet because it may be that the broken page was cached.
disabled both, not working
I can easily reproduce the issue if I try to manually throw an exception in the style sanitizer. But I then see a fatal error added to the PHP error log. Are you seeing the error log populated when you intentionally throw an error on non-AMP pages?
I can see the log is being populated with php errors and warnings, nothing related to AMP, but not sure how to intentionally throw an error for this.
I’ve started a pull request to try to help with detecting this: https://github.com/ampproject/amp-wp/pull/4629
Are you able to edit the AMP plugin’s
includes/class-amp-theme-support.php
file to modify thefinish_output_buffering
method as shown here: https://github.com/ampproject/amp-wp/pull/4629/filesIf you have
WP_DEBUG
enabled then you should see the error displayed.if you append the url with “?debug=true” you can see the errors for yourself. I made that change the amp file, but don’t believe it did anything
Yeah, it doesn’t seem the issue is an exception being thrown when calling
preapre_response
.Another possibility: it could be that output buffering isn’t able to start in the first place.
I’ve made another change to that PR. Could you please try making this additional change to the
start_output_buffering
method in that same file: https://github.com/ampproject/amp-wp/pull/4629/files#diff-2585472f207548f626a43a7ff3cab922added to the file, didnt change anything.
OK, that’s strange.
For added sanity check, above where you added:
if ( ! ob_start( [ __CLASS__, 'finish_output_buffering' ] ) ) { wp_die( esc_html__( 'AMP plugin unable to start output buffering.', 'amp' ) ); }
Please add before:
if ( isset( $_GET['verify_start_output_buffering_called'] ) ) { wp_die( 'Yes, start_output_buffering was called.' ); }
Then we can verify that method is actually being called by making a request with
?verify_start_output_buffering_called=1
that is running
- The topic ‘1.5.3 Update Issues’ is closed to new replies.