Alias79

Yes, it’s weird. I also have Twitter Blue associated with my website account, that surely has nothing to do with it.

I’m in the same situation. Yesterday I left a post on the developers forum (https://twittercommunity.com/t/applicationreceived/191949/23), because there was no way to log into the portal, and they said that they were working on solving that problem. Now is accessible again! I have created the app, and it connects… but it tells me exactly the same as @gtroquilho.

403 Forbidden: The request is understood, but has been refused by Twitter. (Error Code: 453: You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product)

Could it be because WP to Twitter doesn’t support API 2? It seems so, right?

Same here ?? Curiously, the API that I had created for years has disappeared, I suppose because everything has been updated to API V2 and a new one has to be created. I’ve already requested it… but I’ve read people saying that WP to Twitter might not be compatible right now with V2.

Much encouragement to Joseph Dolson!!! All my respect and support, I would even understand if you didn’t want to continue the project. All this mess with the APIs that Twitter has formed is not helping anyone, Twitter itself is the most affected.

I haven’t had time to test it :((( But I’m seeing a lot more people getting it after the last version, so I’m assuming it must be related to version 20.9.

@monbauza I would have loved to do this tests, the problem is the time to do them. This weekend I will try to take time to probe it, and I will comment here if the conflict comes from an incompatibility with another plugin.

When I have problems I use the Health Check and Troubleshooting plugin, so I just need a little time, and notify my editors (because when I update to version 20.9, they will not be able to use SEO, even if only I am in the mode depuration).

The exact same thing happened to me when the update came out. I came here, and I saw a couple of users who had the same thing. I installed the WP Rollback plugin, which lets you choose the version of the plugin you want to rollback to, I reverted to 20.8, and all is well.

Before rolling back, I tried to clear browser cache, and server cache (including my CDN system), but the error remained. It was back to 20.8, and everything works again. I am a user of the classic editor, the truth is that I did not test if it worked with the (horrible) block editor or not.

By the way, I would like to take this opportunity to congratulate the Yoast team for their work and all the time you dedicate to helping people to position their content better through this plugin. This is just a small problem that they will surely find a solution to, as with previous errors, we simply have to be patient (and rollback to the previous version).

The exact same thing happened to me when the update came out. I came here, and I saw a couple of users who had the same thing. I installed the WP Rollback plugin, which lets you choose the version of the plugin you want to rollback to, I reverted to 20.8, and all is well.

Confirmed, it’s a ZEEN theme issue. Its developer has commented that he is working on fixing the problem with Login with Ajax

If you think about it, it’s difficult to use safe mode, and try this ??

You can login from the classic WordPress login. What doesn’t work is the login from the Login with Ajax menu. If you activate safe mode, you can’t check if this fails, since you have to log out to test it, and then you don’t see safe mode.

In my case, I have tried to disable the cache plugins (WP Rocket and the EWWWW CDN), and security (iThemes Security), and some other plugin, and it does not work, I have not been able to do more tests. It could also be a bug in the WordPress theme, “Zeen”, which was just updated yesterday.

It must be for update 5.6. Last night I applied it, and today nobody can log into my website; When entering name and password in Login to Ajax screen, it gives an error message as if you had left any field blank. Through the WP classic login screen, it does allow you to login.

Two more questions: buying full access, would the responsive ads be activated, and would it already work?

On the other hand, do you have a promotion code for the purchase? Right now it is complicated for me, the benefit of this campaign is less than the disbursement of the plugin, and possibly it will only be to use in this campaign (doing this campaign is more for commitment, than for anything else). If you have a discount code I think about it, I want to study all the possibilities.

Hi Joachim!

Thanks for your response!

No, no, Adsense advertising is inserted automatically with Google Site Kit. If you enter the indicated URL from mobile, you will see that there are some ads before the content and after the second paragraph that do not load in AMP

I’m trying to use AMP ads for a mobile campaign, but they appear invisible on AMP pages; the space is reserved, and you can click on it, but you can’t see the banner, it’s invisible.

Example:
https://www.nextn.es/2020/10/semana-de-la-animacion-2020-pokemon-go-detalles/
https://www.nextn.es/2020/10/semana-de-la-animacion-2020-pokemon-go-detalles/amp/

It’s a shame that there is no support these errors keep popping up every day with this plugin ??

There is no solution for this? We constantly see this error with each publication.