Hi, todays update didn´t work for us, we had v2.0.0, as we had to roll back after 2.1.0 update, as we could manage to make it work at all.
Today we gaved a new try with this last update 2.1.1 and faced same problem, we can´t post any tweet. WE tryed to update details at twitter developers portal and then at our site and reconnect, but tweets are not being sended.
Can you please help us, as we cannot roll back againg and we lost completly this option of autosharing tweets.
Maybe this information helps, we do not get any error, we updated the Callback URLs, reconnected the app to twitter, and enabled the account and autopost. Then we went to a post and pressed on “Tweet againg” and nothing happens, it doesn´t send it and either doesn´t show any error.
Ok, I think we found the problem! If you open a post that was already published and we press on: “Tweet again”, it doesn´t do it, BUT if you configure that post to republish globaly a certain time, then it indeed republished back again the retweet. So, you option at posts that says Tweet again, doesn´t work. Could you please check?
I’m currently unable to replicate the issue you mentioned regarding “Tweet again.” To assist you better, could you please provide the following information? This will help us investigate the issue more effectively:
Editor: Are you using the Block editor or the Classic editor?
Console Errors: Have you come across any JavaScript errors in the browser console? You can check this by right-clicking anywhere on the page, selecting “Inspect,” and then navigating to the “Console” tab (OR Press Command+Option+J (Mac) or Control+Shift+J (Windows, Linux, Chrome OS)). Any error messages there would be valuable for our investigation.
Screenshot/Screencast: If possible, could you share a screenshot or screencast of the issue? This would provide us with a clearer understanding of the problem you’re encountering.
We use classic editor. We do not use blocks editor.
At console, we don´t have any errors from your plugin, only from Adsense ads that google doesn´t like, weird but is as it is 😀
and, you will not beleive, but we tested the option of tweet again once more for recording you a few secs video, but when proceeding today and pressing Tweet again, IT WORKED! Yes, it did, don´t know why yesterday during all day didn´t work, but today it did, so everything is working like charm now.
Hey, @dharm1025, I have the same problem described by @ibiza69 in this topic: after updating from 2.0.0 to 2.1.1 the “Tweet Again” button just stopped working… When we click on it, nothing happens (the post isn’t tweeted and there is no error message).
Due to my company policy, I can’t enable the option to autotweet when the post is published (our users do it, at a determined time, using the “Tweet Again” button)…
We are using the Classic Editor and got some alerts and one error in console log, but none of them seems to be related to the plugin.
I’ve tried to enable/disable options and also removed and re-added out twitter account. Nothing fixed the problem to most of the posts I’ve tryed…
In ONE POST, though, after I unchecked the “Use feature image” box, the button worked and the post was tweeted (see pic bellow).
Then I did the same thing in other posts and the button didn’t worked…
Could you please help me investigate what is causing this issue? Thanks,
Thank you for reporting the issue, and apologies for any inconvenience that may have occurred.
In a recent release, we encountered one minor bug that caused the Twitter accounts option to be hidden in the “Tweet Again” meta box. As a result, if accounts are not enabled for “Autoshare by default” in the settings, tweets will not be posted to Twitter using Tweet again.
We have already addressed and resolved this issue. The fix will be included in the upcoming release. In the meantime, could you please enable the “Autoshare by default” option for your accounts to ensure it works as intended? Alternatively, you can use the Block editor, where this issue does not occur.
We hope this solution resolves the problem for you.
Thank you.
Viewing 7 replies - 1 through 7 (of 7 total)
The topic ‘Las version didn´t work for us’ is closed to new replies.
