Error code: AMP_NOT_REQUESTED

Hello @halburgissnet

Thank you for the support topic, As we checked your site it seems to be serving non-AMP pages on URL with ?amp query parameter.

Can you please disable your cache plugin and check if the AMP test validates.

Additionally, please send your site health information using this form so we can investigate the issue further.

Validation results with cache disabled:

Non-AMP submitted
This page isn't an AMP. However, it references the following URL as its AMP version:
https://www.methodsmachine.com/blog/methods-machine-tools-and-yasda-unveil-high-precision-5-axis-machining-center/?amp

Thanks. As I said, this was working fine until recently.

Hello @halburgissnet

Thank you for the site info, We tried to replicate your setup but were unable to do so as there are some commercial/ custom developed plugins and themes on your site which we don’t have, themes and plugins developed specifically by DBS Interactive are out of our reach.

To narrow down further, could you use the Health Check & Troubleshooting plugin and enable its troubleshooting mode. This mode disables active plugins and switches to a default theme safely since it only affects the experience of the logged-in user.

– Please enable the AMP plugin and let me know if the issue is present.
– Enabling 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.

Unfortunately there is no ftp on this server which seems to be required, and I can’t get permissions to add it. We haven’t used it in years. Is there another option? thx

FTP access for your site isn’t required for the Health Check & Troubleshooting plugin. You should be able to find the plugin in the WordPress plugin repository (Plugins > Add New > Health Check & Troubleshooting > Search).

Let me know if you’re unable to locate or install it.

The plugin installs and activates just fine, but clicking on anything that says “troubleshooting” will say …

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.

I do not see a way around that.

Thanks for the update. From what I gather this message can appear if your WordPress site does not have required write permission, in your cases with the wp-content or plugins folder.

Rather than troubleshooting this for the sake of activating another plugin can you try and use the AMP plugins suppression feature to suppress your caching and other plugins before checking once more (AMP > Settings > Plugin Suppression)?

Well, that ftp error reminded me of another plugin which had instructions to get around that requiremnt …

define( ‘FS_METHOD’, ‘direct’ );
define( ‘FS_CHMOD_DIR’, 0775 );
define( ‘FS_CHMOD_FILE’, 0664 );

FYI …

which did allow Troubleshooting mode. Disabling Theme did not help and disabling all the other plugins did not help either. Same error message.

And suppressing all plugins in Settings did not help either. Still getting the “stale results” stuff which is weird too. I’ve also tried disabling/enabling AMP plugin.

Hello @halburgissnet

I will recommend contacting your hosting provider and correct file permissions, so we can further investigate your issue.

This is self hosted, we can change them to anything we want (within reason). But they are no different now than before the upgrade that seems like it started this problem. What needs to change?

Hello @halburgissnet

Can you please verify if there are any rules you have added OR added by another plugin that ignores query parameters ?amp

The query parameter for search is working as expected ?s=hello

Additionally can you please switch Paired URL structure to default ?amp=1 or path suffix /amp/ in AMP plugin settings.

The search ?s=test works fine. Unless the upgrade to WP changed something, there is nothing we did intentionally to mess with this.

?amp=1 does not work …. but … get ready … /amp/ does!!!!! Wow. Thanks. Still curious why / how it broke.