Compatibility Error
-
I am seeing a compatibility issue on my last several Google Web Stories.
I see the attached error in the console, but I do not know what it means. Please recommend next steps for troubleshooting.
Error: “Failed to load resource: the server responded with a status of 404 (Not Found): load-scripts.php?c=1&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils,moxiejs,plupload&ver=5.9.3”
The page I need help with: [log in to see the link]
-
Hi @travelswithted thanks for reaching out. When running your story through AMP validation it passes with no issues. You can see the results here: https://search.google.com/test/amp/result?id=XMpj3Pb_1d7-4Ly5Hjn8qA.
The error you have highlighted from your console looks like WordPress cannot find a particular resource it is expecting. This unfortunately falls outside the scope of our plugin support. I would recommend reaching out to your website developer if you have one or your hosting provider for more assistance with this.
You could also check this guide which has some more information on these sorts of errors and some tips on how you may resolve this issue.
Hope you can manage to resolve this issue and please do let me know if you have any further issues or questions on the Web Stories plugin and I will be happy to help out where I can.
I realized I was not able to attach an image and therefore did not explain the issue well.
The issue is within the web stories plug-in. I am seeing the compatibility error on the checklist after publishing stories. And none of my new (past few days) stories are getting traffic despite being indexed.
I provided the console error because I had seen that data requested for another user having similar issues.
@travelswithted Thanks for clarifying. To share a screenshot of this you can use a service such as Imgur to share an image link or share via a Google Drive link. This would be helpful if you could share.
Could you also let me know if you are seeing any other console errors in the browser? #
If you could also please share your Site Health information or You can share privately if you prefer via this form.
Thank you!
Here is a link to screenshot of the error: https://imgur.com/a/YId6U8C
the only other console error says “8916.js?ver=18f51494b732a1f8c75e0b4a5d4ae389:23 [Web Stories] Tracking event “load_media” took too long to fire.”
Here is the site health info:
`
### wp-core ###version: 5.9.3
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 1
dotorg_communication: true### wp-paths-sizes ###
wordpress_path: /www/travelswithted_768/public
wordpress_size: 914.76 MB (959192636 bytes)
uploads_path: /www/travelswithted_768/public/wp-content/uploads
uploads_size: 2.46 GB (2642785150 bytes)
themes_path: /www/travelswithted_768/public/wp-content/themes
themes_size: 13.12 MB (13759101 bytes)
plugins_path: /www/travelswithted_768/public/wp-content/plugins
plugins_size: 91.32 MB (95751811 bytes)
database_size: 720.94 MB (755957760 bytes)
total_size: 4.16 GB (4467446458 bytes)### wp-active-theme ###
name: GeneratePress (generatepress)
version: 3.1.3
author: Tom Usborne
author_website: https://tomusborne.com
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, automatic-feed-links, post-thumbnails, post-formats, woocommerce, title-tag, html5, customize-selective-refresh-widgets, align-wide, responsive-embeds, editor-color-palette, custom-logo, menus, editor-styles, editor-style, widgets
theme_path: /www/travelswithted_768/public/wp-content/themes/generatepress
auto_update: Enabled### wp-themes-inactive (4) ###
Twenty Nineteen: version: 2.0, author: the WordPress team (latest version: 2.2), Auto-updates disabled
Twenty Twenty: version: 1.7, author: the WordPress team (latest version: 1.9), Auto-updates disabled
Twenty Twenty-One: version: 1.5, author: the WordPress team, Auto-updates enabled
Twenty Twenty-Two: version: 1.0, author: the WordPress team (latest version: 1.1), Auto-updates disabled### wp-mu-plugins (2) ###
Kinsta Must-use Plugins: version: 2.3.6, author: Kinsta Team
SSO: version: 0.3, author: Garth Mortensen, Mike Hansen### wp-plugins-active (20) ###
Ads.txt Manager: version: 1.0.9, author: Ads.txt Manager <[email protected]>, Auto-updates enabled
Advanced Editor Tools (previously TinyMCE Advanced): version: 5.6.0, author: Automattic, Auto-updates enabled
Broken Link Checker: version: 1.11.16, author: WPMU DEV, Auto-updates disabled
Code Snippets: version: 2.14.3, author: Code Snippets Pro, Auto-updates enabled
Contextual Related Posts: version: 3.1.1, author: WebberZone, Auto-updates enabled
Cost Calculator: version: 2.3.7, author: BoldThemes, Auto-updates enabled
Flying Scripts by WP Speed Matters: version: 1.2.2, author: Gijo Varghese, Auto-updates enabled
FMTC Affiliate Disclosure: version: 2.0.3, author: Eric Nagel, Auto-updates enabled
GP Premium: version: 2.1.2, author: Tom Usborne, Auto-updates enabled
Insert Headers and Footers: version: 1.6.0, author: WPBeginner, Auto-updates enabled
MC4WP: Mailchimp for WordPress: version: 4.8.7, author: ibericode, Auto-updates enabled
Rank Math SEO: version: 1.0.87, author: Rank Math, Auto-updates enabled
RSS Importer: version: 0.2, author: wordpressdotorg, Auto-updates enabled
Sassy Social Share: version: 3.3.40, author: Team Heateor, Auto-updates enabled
Smush: version: 3.9.5, author: WPMU DEV, Auto-updates enabled
Table of Contents Plus: version: 2106, author: Michael Tran, Auto-updates enabled
UpdraftPlus – Backup/Restore: version: 1.22.11, author: UpdraftPlus.Com, DavidAnderson, Auto-updates enabled
Web Stories: version: 1.19.0, author: Google, Auto-updates enabled
WPForms Lite: version: 1.7.3, author: WPForms, Auto-updates enabled
WPS Hide Login: version: 1.9.4, author: WPServeur, NicolasKulka, wpformation, Auto-updates enabled### wp-plugins-inactive (2) ###
Ezoic: version: 2.7.3, author: Ezoic Inc., Auto-updates disabled
Public Post Preview: version: 2.9.3, author: Dominik Schilling, Auto-updates enabled### wp-media ###
image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
imagick_version: 3.5.1
file_uploads: File uploads is turned off
post_max_size: 128M
upload_max_filesize: 128M
max_effective_size: 128 MB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 122 MB
imagick::RESOURCETYPE_DISK: 1073741824
imagick::RESOURCETYPE_FILE: 768
imagick::RESOURCETYPE_MAP: 512 MB
imagick::RESOURCETYPE_MEMORY: 256 MB
imagick::RESOURCETYPE_THREAD: 1
imagemagick_file_formats: 3FR, 3G2, 3GP, AAI, AI, ART, ARW, AVI, AVS, BGR, BGRA, BGRO, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CRW, CUR, CUT, DATA, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FILE, FITS, FRACTAL, FTP, FTS, G3, G4, GIF, GIF87, GRADIENT, GRAY, GRAYA, GROUP4, GV, H, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, HTTP, HTTPS, ICB, ICO, ICON, IIQ, INFO, INLINE, IPL, ISOBRL, ISOBRL6, JBG, JBIG, JNG, JNX, JPE, JPEG, JPG, JPS, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAGICK, MAP, MASK, MAT, MATTE, MEF, MIFF, MKV, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PGX, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UBRL6, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WEBP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
gd_version: 2.3.0
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: unknown### wp-server ###
server_architecture: Linux 5.13.0-1023-gcp x86_64
httpd_software: nginx/1.21.3
php_version: 7.4.25 64bit
php_sapi: fpm-fcgi
max_input_variables: 10000
time_limit: 300
memory_limit: 256M
max_input_time: 300
upload_max_filesize: 128M
php_post_max_size: 128M
curl_version: 7.68.0 OpenSSL/1.1.1f
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true### wp-database ###
extension: mysqli
server_version: 10.5.12-MariaDB-1:10.5.12+maria~focal
client_version: mysqlnd 7.4.25
max_allowed_packet: 33554432
max_connections: 10### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /www/travelswithted_768/public/wp-content
WP_PLUGIN_DIR: /www/travelswithted_768/public/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
DB_CHARSET: utf8
DB_COLLATE: undefined### wp-filesystem ###
wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable### web_stories ###
web_stories_version: 1.19.0
web_stories_db_version: 3.0.14
web_stories_amp_version: 2.3.0-alpha
web_stories_cdn_url: https://wp.stories.google/static/15
web_stories_dev_mode: false
web_stories_theme_support: Disabled
web_stories_enabled_experiments:
Story locking: Enabled
CORS check: Enabled
Updated Publish Story Modal: Enabled
Custom Fonts: Enabled
Page Background Audio: Enabled
Floating Menu: Enabled
Deleted Fonts: Enabled
web_stories_libxml_version: 2.9.12### wpforms ###
version: 1.7.3
lite: Mar 11, 2019 @ 6:32pm
upload_dir: Writable
db_tables: _S6K_wpforms_tasks_meta
total_forms: 1
total_submissions: undefined@travelswithted thanks for all the information which is very helpful. This could be due to a plugin conflict so to rule this out could you try following the steps below and let me know if you still get the compatibility warning.
Use the Health Check & Troubleshooting plugin and enable its troubleshooting mode. This mode disables active plugins and switches to a default theme safely because it only affects the experience of the logged-in user.
- Please enable the Web Stories plugin and let me know if you still get the issue.
- Enable plugins and your theme one by one in this mode may help pinpoint if something else is involved.
- Note you can disable troubleshooting mode from the plugins page.
These steps will not affect what a user to your site will see while testing this. Let me know how you get on here and if you have any questions.
The error message is still present in troubleshooting mode with all plugins disabled.
@travelswithted thanks for trying this and sorry to hear this hasn’t cleared the warning. In cases where issues are related to AMP validation errors the health check and troubleshooting plugin won’t highlight a plugin conflict so it would also be helpful at this point to try manually deactivating plugins.
If possible could you try manually deactivating plugins one by one and checking back in your Web Stories editor to see if at any point the warning clears.
In the meantime I will discuss this internally with the team and update you as soon as I can.
I have already tried manually deactivating plugins and the error is still present.
I also run all stories through Google’s amp test and have never had an amp issue.Hi @travelswithted and thanks for your effort in troubleshooting and patience while I discussed this with the team.
As your story is passing AMP validation I can confirm that the “compatibility” warning you are seeing in the editor checklist can in this case be ignored. If your story is passing the AMP validation then it is valid.
It would be useful if possible and if you feel comfortable with this, to follow the steps below and report your findings.
- Go to your Web Stories editor where you are seeing the “compatibility” warning
- Press the F12 key to open your browser dev tools
- Navigate to the ‘console‘ tab
- Paste the following code into the console section and hit enter
https://www.travelswithted.com/web-stories/what-type-of-rv-is-right-for-your-family/ - Share the results you get back here
Please let me know if you have any questions.
Thanks Adam.
Above you say to paste a code, but then just show a URL. Is that correct?@travelswithted apologies that’s not the correct code to paste good spot! Please ignore that and use this instead:
await window.amp.validator.validateUrlAndLog('https://www.travelswithted.com/web-stories/what-type-of-rv-is-right-for-your-family/')Thank you. Below is the result.
validator_wasm.js?ver=1.19.0:1830 AMP validation had errors: module$contents$amp$validator_logValidationResult @ validator_wasm.js?ver=1.19.0:1830 (anonymous) @ validator_wasm.js?ver=1.19.0:1833 $jscomp.generator.Engine_.nextStep_ @ validator_wasm.js?ver=1.19.0:29 $jscomp.generator.Engine_.next_ @ validator_wasm.js?ver=1.19.0:25 next @ validator_wasm.js?ver=1.19.0:30 b @ validator_wasm.js?ver=1.19.0:31 Promise.then (async) f @ validator_wasm.js?ver=1.19.0:31 Promise.then (async) f @ validator_wasm.js?ver=1.19.0:31 (anonymous) @ validator_wasm.js?ver=1.19.0:31 $jscomp.asyncExecutePromiseGenerator @ validator_wasm.js?ver=1.19.0:31 $jscomp.asyncExecutePromiseGeneratorProgram @ validator_wasm.js?ver=1.19.0:31 module$contents$amp$validator_validateUrlAndLog @ validator_wasm.js?ver=1.19.0:1832 (anonymous) @ VM112:1 validator_wasm.js?ver=1.19.0:1831 https://www.travelswithted.com/web-stories/what-type-of-rv-is-right-for-your-family/:2:0 Custom JavaScript is not allowed. (see https://amp.dev/documentation/guides-and-tutorials/learn/validation-workflow/validation_errors/#custom-javascript-is-not-allowed) module$contents$amp$validator_logValidationResult @ validator_wasm.js?ver=1.19.0:1831 (anonymous) @ validator_wasm.js?ver=1.19.0:1833 $jscomp.generator.Engine_.nextStep_ @ validator_wasm.js?ver=1.19.0:29 $jscomp.generator.Engine_.next_ @ validator_wasm.js?ver=1.19.0:25 next @ validator_wasm.js?ver=1.19.0:30 b @ validator_wasm.js?ver=1.19.0:31 Promise.then (async) f @ validator_wasm.js?ver=1.19.0:31 Promise.then (async) f @ validator_wasm.js?ver=1.19.0:31 (anonymous) @ validator_wasm.js?ver=1.19.0:31 $jscomp.asyncExecutePromiseGenerator @ validator_wasm.js?ver=1.19.0:31 $jscomp.asyncExecutePromiseGeneratorProgram @ validator_wasm.js?ver=1.19.0:31 module$contents$amp$validator_validateUrlAndLog @ validator_wasm.js?ver=1.19.0:1832 (anonymous) @ VM112:1 validator_wasm.js?ver=1.19.0:1831 See also https://validator.amp.dev/?experimental_wasm=1#url=https%3A%2F%2Fwww.travelswithted.com%2Fweb-stories%2Fwhat-type-of-rv-is-right-for-your-family%2F@travelswithted thanks for providing this. We are looking into if this can be prevented but as mentioned above you can ignore this as your stories are passing AMP validation.
Thank you!
Hi. To update this topic. I still see the compatibility error and as of last week, I am seeing a new issue that may or may not be related. My web stories were passing core web vitals until 5/13/22. However, now all of my web stories are showing LCP is too long.
I have not made any changes to my site aside from publishing new posts/stories.
Please suggest any optimizations.
The topic ‘Compatibility Error’ is closed to new replies.
