Notice after update
-
Since installing the latest update, my website shows this kind of notice to everyone:
Notice: amp_is_available wurde fehlerhaft aufgerufen. amp_is_available() (or amp_is_request(), formerly is_amp_endpoint()) was called too early and so it will not work properly. WordPress is currently doing the “pre_get_posts” action. Calling this function before the “wp” action means it will not have access to WP_Query and the queried object to determine if it is an AMP response, thus neither the “amp_skip_post()” filter nor the AMP enabled toggle will be considered. Weitere Informationen: Debugging in WordPress (engl.) (Diese Meldung wurde in Version 2.0.0 hinzugefügt.) in /srv/www/cleanthinking/wp-includes/functions.php on line 5225
How can we solve this?
Martin
The page I need help with: [log in to see the link]
-
Sorry to hear you’ve been encountering trouble. This may be a third party plugin causing this notice. Can you enable the AMP plugin and then share your Site Health information so we can see if we can help identify the cause? You can use this form to share privately if preferred. Using the same form you can also share your error log.
In the meantime if you want to keep the plugin enabled can you inform me if the notice appears for users if you turn off front end error reporting via the following?
define( 'WP_DEBUG_DISPLAY', false );You’ll find instructions here.
One information: I disabled all other plugins, but the problem further occured.
Here is my Site Health Information:
### wp-core ###
version: 5.5
site_language: de_DE
user_language: de_DE
timezone: Europe/Berlin
permalink: /%postname%/
https_status: true
user_registration: 0
blog_public: 1
default_comment_status: open
multisite: false
user_count: 9
dotorg_communication: true### wp-paths-sizes ###
wordpress_path: /srv/www/cleanthinking
wordpress_size: 3,53 GB (3790336420 bytes)
uploads_path: /srv/www/cleanthinking/wp-content/uploads
uploads_size: 1,46 GB (1571984138 bytes)
themes_path: /srv/www/cleanthinking/wp-content/themes
themes_size: 78,92 MB (82753316 bytes)
plugins_path: /srv/www/cleanthinking/wp-content/plugins
plugins_size: 85,54 MB (89691294 bytes)
database_size: 968,35 MB (1015385717 bytes)
total_size: 6,10 GB (6550150885 bytes)### wp-active-theme ###
name: Publisher (publisher)
version: 7.7.0
author: BetterStudio
author_website: http://betterstudio.com/
parent_theme: none
theme_features: core-block-patterns, title-tag, html5, post-thumbnails, post-formats, automatic-feed-links, menus, editor-style, widgets
theme_path: /srv/www/cleanthinking/wp-content/themes/publisher
auto_update: Deaktiviert### wp-themes-inactive (1) ###
Twenty Twenty: version: 1.5, author: WordPress-Team,Automatische Aktualisierungen deaktiviert
### wp-plugins-active (24) ###
404page – your smart custom 404 error page: version: 11.2.6, author: Peter Raschendorfer, Automatische Aktualisierung aktiviert
AAWP: version: 3.13, author: AAWP, Automatische Aktualisierung aktiviert
Akismet Anti-Spam: version: 4.1.6, author: Automattic, Automatische Aktualisierung aktiviert
AMP: version: 2.0.0, author: AMP Project Contributors, Automatische Aktualisierungen deaktiviert
Better Ads Manager: version: 1.19.4, author: BetterStudio, Automatische Aktualisierungen deaktiviert
Better Post Views: version: 1.6.0, author: BetterStudio, Automatische Aktualisierungen deaktiviert
Better Social Counter Widget: version: 1.13.1, author: BetterStudio, Automatische Aktualisierungen deaktiviert
Check Email: version: 0.6.1, author: MachoThemes, Automatische Aktualisierung aktiviert
Cookiebot | GDPR/CCPA Compliant Cookie Consent and Control: version: 3.7.1, author: Cybot A/S, Automatische Aktualisierung aktiviert
Custom Sidebars: version: 3.2.3, author: WPMU DEV, Automatische Aktualisierungen deaktiviert
Disable Feeds: version: 1.4.4, author: Samir Shah, BBpress support by Matthew Sigley, Automatische Aktualisierung aktiviert
Facebook Pixel: version: 1.6.0, author: Facebook, Automatische Aktualisierungen deaktiviert
Hummingbird Pro: version: 2.5.3, author: WPMU DEV, Automatische Aktualisierungen deaktiviert
Newsletter, SMTP, Email marketing and Subscribe forms by Sendinblue: version: 3.0.6, author: Sendinblue, Automatische Aktualisierung aktiviert
Smush Pro: version: 3.6.3, author: WPMU DEV, Automatische Aktualisierungen deaktiviert
SubHeading: version: 1.8.1, author: StvWhtly, Automatische Aktualisierung aktiviert
TablePress: version: 1.12, author: Tobias Bäthge, Automatische Aktualisierung aktiviert
wp-worthy: version: 1.5.6.1, author: tiggersWelt.net, Automatische Aktualisierung aktiviert
WPBakery Page Builder: version: 6.2.0, author: Michael M – WPBakery.com, Automatische Aktualisierungen deaktiviert
WPMU DEV Dashboard: version: 4.10.0, author: WPMU DEV, Automatische Aktualisierungen deaktiviert
WP PayPal: version: 1.2.2.5, author: naa986, Automatische Aktualisierung aktiviert
Yoast Duplicate Post: version: 3.2.5, author: Enrico Battocchi & Team Yoast, Automatische Aktualisierung aktiviert
Yoast SEO: News: version: 12.6, author: Team Yoast, Automatische Aktualisierungen deaktiviert
Yoast SEO Premium: version: 14.8.1, author: Team Yoast, Automatische Aktualisierungen deaktiviert### wp-media ###
image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1673
imagemagick_version: ImageMagick 6.8.9-9 Q16 x86_64 2019-11-12 http://www.imagemagick.org
file_uploads: File uploads is turned off
post_max_size: 8M
upload_max_filesize: 2M
max_effective_size: 2 MB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 63 GB
imagick::RESOURCETYPE_DISK: 1.844674407371E+19
imagick::RESOURCETYPE_FILE: 768
imagick::RESOURCETYPE_MAP: 63 GB
imagick::RESOURCETYPE_MEMORY: 31 GB
imagick::RESOURCETYPE_THREAD: 8
gd_version: 2.3.0
ghostscript_version: 9.26### wp-server ###
server_architecture: Linux 4.4.0-169-generic x86_64
httpd_software: Apache
php_version: 7.4.6 64bit
php_sapi: fpm-fcgi
max_input_variables: 1000
time_limit: 30
memory_limit: 512M
max_input_time: 60
upload_max_size: 2M
php_post_max_size: 8M
curl_version: 7.47.0 OpenSSL/1.0.2g
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true### wp-database ###
extension: mysqli
server_version: 5.6.26-74.0
client_version: mysqlnd 7.4.6### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /srv/www/cleanthinking/wp-content
WP_PLUGIN_DIR: /srv/www/cleanthinking/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: true
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: true
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: transitional
amp_reader_theme: legacy
amp_templates_enabled: post, page, attachment, is_singular, is_front_page, is_archive, is_search, is_404, is_category, is_tag
amp_serve_all_templates: false
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: 1180
amp_css_transient_caching_time_series:
20200814: 467
20200815: 462
20200816: 431
20200817: 433
20200818: 422
20200819: 400
20200820: 397
20200821: 377
20200822: 353
20200823: 353
20200824: 354
20200825: 337
20200826: 335
20200827: 1176
amp_libxml_version: 2.9.10`
I added the “Display = False” Code to the wpconfig and now, the message disappeared.
One of the plugins or the theme is calling
is_amp_endpoint()at thepre_get_postsaction. We’ll try to identify which one is doing so. It’s something the theme/plugin will need to fix.Hi, @cleanthinking. It appears that the BetterStudio core theme is the source of this issue, as it is calling
is_amp_endpointon thepre_get_postshook. The best way to resolve this will be to reach out to the theme developer and let them knowis_amp_endpointshould not be called after thewphook.
The topic ‘Notice after update’ is closed to new replies.