paulogoncalves

I’m using WP version 6.0. Theme and all plugins except Yost are up to date. I always keep WP, theme and plugins up to date. This problem has occurred before. About a year ago on the 16.2 update See this topic:
https://www.ads-software.com/support/topic/yoast-seo-tabs-do-not-open-when-editing-a-post/

@lordj12
To return the previous version of any plugin I use another plugin: the WP Rollback

https://br.www.ads-software.com/plugins/wp-rollback/

I have the same problem. With the Classic Editor the SEO tabs do not open and with the Block Editor the page for editing does not open and presents an error message “the editor has encountered an unexpected error”

I returned the plugin version to 16.1.1 and both the Classic Editor and the Block Editor work.

The problem is in later versions of the plugin.

After enabling WP-DEBUG I realized that there was a conflict between the PushNotifcations.io plugin and the OneSignal Push plugin. I uninstalled the PushNotifcations.io plugin and with that the AMP pages returned to working normally. I appreciate the attention.

the problem persists in all the latest versions of the plugin. As I reported earlier, I am currently using version 1.0.76 which is the last one that works. The other later versions DO NOT WORK. With them, a white screen is displayed with a serious error message on the website and Goggle INVALID all AMP pages

o problema persiste em todas as ultimas versōes do plugin. Conforme informei anteriormente estou no momento utilizando a versāo 1.0.76 que é a ultima que funciona. As demais versōes posteriores NāO FUNCIONAM. Com elas é exibida uma tela branca com a mensagem de erro grave no site e o Goggle INVALIDA todas as paginas AMP.

A breve informa??o prometida em sua ultima mensagem até hoje n?o chegou

The brief information promised in your last message to date has not arrived

I installed the WP Rollback plugin and returned the version of the plugin AMP for WP to 1.0.76 With this the AMP version of the pages returned to work. But I had to turn off the automatic update and I can no longer update this the summer of this plugin, which is not recommended. I would like the problem to be solved in a new version of the plugin and to be advised to update the plugin.

O Google Search Console passou a invalidar as páginas AMP. Creio que o problema requer rápida solu??o. Por favor, poderia priorizar a solu??o deste problema.

Google Search Console went on to invalidate AMP pages. I believe that the problem requires a quick solution. Please, you could prioritize the solution of this problem.

The version used is 10.1.0.76.9 according to the last update made available three days ago. I didn’t find instructions to revert to the previous version and I don’t know how to do this. If necessary, please send me instructions to do this.

the problem has not been resolved. the solution that you suggested was to disable the function that has a problem. But the problem remains because the error has not been corrected.

My AMP pages elevated by the AMP plugin for WP were all validated by Google Search Console. After updating the plugin for Google Search Console, he started to notify me that my AMP pages are not valid. It has frequent flaws such as: “The HTML tag has an attribute or attribute value that is not allowed.”

The Google Search Console AMP Page Validator (https://search.google.com/test/amp) also has a flaw: The “value” attribute may not appear in the “meta” tag.

To confirm, just run a test at the link: https://search.google.com/test/amp with this URL: https://programeviagem.com/amp/

After several tests, disabling and reactivating the plugin and clearing all caches, I am sorry to inform you that the problem remains. The images have no alt attribute in the AMP version, although the alt attribute exists in the non-AMP version. The images with this problem are in the Gallery block of the WP editor
This failure is accused by Google Lighthouse in the accessibility audit. What is worse is that other flaws in the AMP version are also found that do not exist in the non-AMP version. The reported failures are:

1. Buttons do not have an accessible name.

2. <frame> or <iframe> elements do not have a title.

3. Image elements do not have [alt] attributes

4. Links do not have a discernible name

Test with Google Lighthouse on this page and note the difference in the results of the AMP version with the Non-AMP version:
AMP version: https://programeviagem.com/destinos-de-viagem/destinos-de-viagem-brasil/atracoes-turisticas-de-alagoas/amp/
Non-AMP version: https://programeviagem.com/destinos-de-viagem/destinos-de-viagem-brasil/atracoes-turisticas-de-alagoas/

I’ll be happy if I have this fix in the next version

From what is seen in the forum of this plugin, it seems that you are only interested in answering and not solving the problems. One hour asks to attach images, another time asks to open a new topic. And absolutely nothing is said about the reported problem. a beautiful way to deceive people!

OneSignal is working perfectly in the non-AMP version. So I was suggested to talk to the AMP plugin support