Thread Starter
wspeed
(@wspeed)
Awesome John, thanks for the clafication.
I see I get only the Id of the redirection that is on the database.
Last, please correct me if I’m wrong, but I should now query the DB with this ID to get the relevant data, instead of redirection_create_redirect and redirection_update_redirect which return $data[‘url’], right?
I see these 2 are called right before saving to the database, so it wouldn’t make sense for me to clear cache of requests not yet run.
Thanks and regards.
Thread Starter
wspeed
(@wspeed)
Hi, I have sent you the data privately on the email.
Let me know if you need anything.
Thread Starter
wspeed
(@wspeed)
Hi, I guess you haven’t seen my previous screenshot, no worries.
Activated Plugins:
– Accelerated Mobile Pages
– Tagdiv Composer (from Newspaper theme)
– Tagdiv Social Counter (from Newspaper Theme)
– TINYMCE Advanced (from Newspaper Theme).
No Contact form 7 plugin, nor anything else is being used.
If you want I can deactivate all plugins and keep only Accelerated Mobile Pages enabled for testing purposes.
Thread Starter
wspeed
(@wspeed)
Hi Ampforwp,
Thanks for your support.
There are no opt-in form plugins installed nor enabled.
For testing purposes, I have upgraded to the latest version the AmpforWP plugin and
deactivated all the other unnecessary plugins.
Still, the issue persists.
Please have a look at the plugins there are enabled right now + the error still happening:
https://www.screencast.com/t/A8YaCTmZ0
Kindly advise.
PS1: I tried using the process described in https://github.com/Automattic/amp-wp/wiki/Handling-Media -> Custom Embed Handler to search&replace amp-mustache-0.1 by 0.2, without success.
Ps2: Moreover, I have deactivated the custom enhancement I already have for correcting amp errors which is the one described in PS1, still no luck.
I might be wrong, but if I would guess, I’d say the plugin needs to be updated to use amp-mustache 0.2 which would solve the warning from google.
Thanks and hopefully I have assisted.
Thread Starter
wspeed
(@wspeed)
Hi Ampforwp, thanks for the update.
I have just updated to 0.9.97.9 and issue persists.
Also, I have cleared the cache so I guarantee that there is no cache impact and yes, regretfully the issue persists.
Here is a screen print of the Chrome Amp Validator + the snippet of the source code.
I have updated this on quality system before going live, I will wait for a couple weeks before testing again.
Thanks for your prompt response.
Best REgards
Hi Team,
I had this problem and I figured out the problem.
You are requesting the file without the .min extension.
As a workaround I copied the file and it opened fine.
I have latest (as of now ) 3.0.11 version.
Please check the screenshot you will understand:
