AMP Settings: Something Went Wrong
-
AMP gets installed successfully, but when I Click AMP Settings it take few minutes and shows this error: “Something Went Wrong. Check your connection and open your browser console to see of there are any error messages. You may share them on the Support Forum.”
-
Thanks for reaching out. So we can determine more on this can you share the following:
- Your Site Health information. You can users our user submission form to share privately if preferred.
- Do you see any browser console errors on your settings page when this occurs? If so please share the messages that appear.
Once we know the above we can provide some troubleshooting suggestions.
Are you running on the latest version of WordPress or an older version? In the just-released v2.2 of the AMP plugin we’ve fixed some issues we discovered with running on older versions of WP. But ideally you’d be upgraded to the latest version of WP to benefit from all improvements and features.
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.
Update: I see you shared your Site Health information.
From checking the details I can see some Rank Math related errors. Does the same occur if you temporarily deactivate Rank Math and then try to access the AMP plugins settings?
I’ve also reopened this support topic.
I don’t use MATH Rank, I use Yoast. When I had installed AMP for the first time it was showing the settings, but later I had removed it. After some weeks I tried to install AMP again, It installs and gets activated, but shows the error instead of Settings.
Debugging information for the Official AMP Plugin for WordPress.
AMP slug query var amp
AMP slug defined late false
AMP mode enabled transitional
AMP Reader theme legacy
Templates enabled post, page, attachment, is_singular, is_front_page, is_home, is_archive, is_author, is_date, is_search, is_404, is_category, is_tag
Serve all templates as AMP? true
Transient caching for stylesheets disabled n/a
Threshold for monitoring stylesheet caching 5000 transients per day
Sampling range for monitoring stylesheet caching 14 days
Number of stylesheet transient cache entries 56
Calculated time series for monitoring the stylesheet caching20210714: 6
20210715: 27
20210716: 52
20211211: 56libxml Version 2.9.7`
I have resolved the error, but I am getting one more Recommendation from WordPress i.e “Page caching is not detected AMP”.
I am using w3Total Cache for performance optimization.
Here is the status
The AMP plugin performs at its best when page caching is enabled. This is because the additional optimizations performed require additional server processing time, and page caching ensures that responses are served quickly.
Page caching is detected by making three requests to the homepage and looking for Cache-Control: max-age=…, Expires, or Age HTTP response headers.”
Thanks
Thanks for the update. If you’re not using Rank Math I wonder it’s possible another user summitted their own Site Health information maybe after landing on this support topic. Regardless glad to hear you were able to determine the cause.
In relation to your page caching query we’ve added documentation to the plugin website that can assist with this. Did you activate the “AMP extension” listed within that documentation?
@meerbasit
As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.W3 Total Cache may not have had had page caching enabled. We tested W3 Total Cache with page caching enabled and it returns this header:
cache-control: max-age=3600, public. That’s what we’re looking for.
The topic ‘AMP Settings: Something Went Wrong’ is closed to new replies.