User is over daily status update limit

Hi, twitter implemented new limits yesterday, the issue would be on twitter’s end, we’re monitoring the discussion to see what happens: https://twittercommunity.com/t/user-is-over-daily-status-update-limit/115380/8

Please try increasing the twitter threshold temporarily example 1 tweet every 12 hours, this is just to confirm that the twitter limits are bugged

Hi all, please try creating a new twitter application according to the instructions here: https://docs.revive.social/article/914-how-to-create-a-twitter-application-for-revive-old-post

Once that application is complete, go to Revive Old Posts plugin dashboard and deactivate the twitter account by turning the switch next to it to the off position. Then after hovering over your profile picture from within the plugin’s accounts area you should see a little bin icon, click that to delete the account.

Then re-add the account by using the credentials from your newly created app from developers.twitter.com

This has worked for some individuals, let us know how it goes

I did all that you asked and that worked but when I went to view the ‘Sharing Queue’ I received this message – It seems there is an issue with your WordPress configuration and the core REST API functionality is not available. This is crucial as Revive Old Posts relies on this functionality in order to work.
The root cause might be either a security plugin which blocks this feature or some faulty server configuration which constrain this WordPress feature.
You can try to disable any of the security plugins that you use in order to see if the issue persists or ask the hosting company to further investigate.

I have changed nothing else

so the ‘Sharing Queue’ will not build a list and I cannot publish anything

@theappwhisperer please send us a ticket here: https://revive.social/support/ enter “Free” where it asks for license.

@michela-fantinel twitter will retire apps.twitter.com, once you create a new app on developer.twitter.com it should be fine

Got it thanks. I think I used developer. twitter, so that’s great to know!

This solution worked for me

I also found this in my blogs, and they send messages every 11 hours.

Queue is built, however, I have not seen a sent message in a week or so.

@myuption if you’re having this issue with all connected accounts and not just twitter which we’ve posted the solution for above then please see this document: https://docs.revive.social/article/686-fix-revive-old-post-not-posting

I applied to create the new Twitter application, following your instructions, but got a message from them that they couldn’t approve it without more information. Is there any other solution?

Uriahs Victor (@uriahs-victor)
?Fantástico, gracias!
Aplicada la solución y ya está funcionando de nuevo.

Wonderful thanks!
Applied the solution and it is already working again.

@uriahs-victor) I do have a cron job setup in my server, that is the way I post content.

I reset everything in onw of my accounts, created my twitter app, then start sharing and ran the cron job manually, both posts were sent. Let’s see how it works on its own… in 13 hours XD

Thanks!

What a nightmare that process is.

So I finally got the super secret API keys, I enter them in, the Revive page reloads, and then nothing.

Did it 5x. No new account is added. Am I doing something wrong?

Isn’t there any other way?

Isn’t this only a workaround until the problem is fixed, or is this the only way to use the plugin in the future?

@bezukhof check your callback URL, make sure it’s the same as what we have in our twitter app creation document. If you still have issues then reach out to us here: https://revive.social/support/

@johannes4711 this isn’t a “workaround” this is actually the solution since twitter changed their platform. New users would not have this issue since in our document for twitter app creation we have the steps for developer.twitter.com

All old users who had apps on apps.twitter.com might run into this issue and would need to migrate to developer.twitter.com

The error itself doesn’t make sense since we know you guys are not hitting the limits, but twitter staff doesn’t seem to acknowledge this so the solution has been to do what I said in my reply.