• ABX

    (@buddha1822)


    As with everyone else here, EVERYTHING is broken. Both Telegram and Twitter updates with this latest update. It’s a disaster. PLEASE FIX THIS. I did NOT need this headache on Monday morning when everything was working fine. There are no errors in the Twitter.

    Twitter – I have done as requested and updated the API, added the old API to the new project, and all the keys stay the same. But the plugin just sits there spinning on “Sending Tweet” and NO error or stop or nothing. Stuck in an endless loop there. No errors in the log either. Nothing at all to work with.

    Telegram – I get THIS error in the log, no explanation as to why or what’s brokek and it’s not mentioned in any of the update places.

    [2022-07-18 09:13:37] [User ID:45] – [Error] [Telegram – Telegram NewsBot] – -=ERROR=- WP_Error Object ( [errors] => Array ( [http_request_failed] => Array ( [0] => cURL error 28: Operation timed out after 45001 milliseconds with 766 out of 1323 bytes received ) ) [error_data] => Array ( ) [additional_data:protected] => Array ( ) ) – ERROR

Viewing 7 replies - 16 through 22 (of 22 total)
  • Plugin Author NextScripts

    (@nextscripts)

    As I just said. Yes, a lot was changed. Latest version is using Twitter API v2. This is the only API that currently available for free without any approvals from Twitter.

    Twitter gives no way for us to check if app is “new” or “old”. Also, both “new” and “old” apps are working fine everywhere we tested them. Obviously you and few other people have something breaking it, that we don’t know yet. As soon as someone will be willing to let us check, we will fix it.

    Thread Starter ABX

    (@buddha1822)

    Thank you for the help solving this. Hopefully we can figure out what’s going on. I’ve submitted my support request on your site, not sure what else there is to do now.

    After updates, Telegram DOES NOT WORK normally!
    Only the picture is published, and the link is not added.

    Same error with cURL error 28.

    At the same time, if you roll back to 4.3.26, then everything works NORMALLY!

    Developers! Fix the problem!`

    Downgrading to version .26 when download this version?

    • This reply was modified 2 years, 4 months ago by werana.
    Thread Starter ABX

    (@buddha1822)

    STILL getting the same Telegram error in .29 despite an investigation. And now Twitter “works” but it runs WAY slower than before. Don’t think much has been fixed yet with this…

    Something is clearly wrong with the latest update.
    There is not much info that we can provide to the support.

    First: the twitter issues are related, mostly, with users that still don’t have a developer account – since SNAP changed to the new Twitter API, this affects everyone that still doesn’t have the account.
    Activate the developer account in Twitter: https://developer.twitter.com/

    After that, move your Twitter app to a New Project, and is done – you can regenerate the keys or not, but try that also.

    Second: There is some issue with curl in SNAP. is timing out fetching or sending content. Images are not being fetch, timing out.
    There is no specific error, just a timeout.
    Sent messages also fail.

    In the meantime, revert to the .26 version. This will fix the issues – also will fix the Twitter issues (since it uses the v1.1 version of the API), but you MUST update your developer account in Twitter ASAP.

    If needed, this is the .26 version: https://mega.nz/file/Y00DzRRS#8DPPwVg2sT7cdIHuaNmrMGklbn8–IrGMu4nIKR8tFc

    Just upload as a new plugin and confirm the file changes – don’t need to remove the most recent version if installed.

    And congrats to the SNAP team to finally get back to support this awesome plugin.
    Hope to see fixes sometime soon. ??

    • This reply was modified 2 years, 4 months ago by DJPRMF.
    • This reply was modified 2 years, 4 months ago by DJPRMF.

    Thanks ABX for the link to the older version, I am also having issues.

Viewing 7 replies - 16 through 22 (of 22 total)
  • The topic ‘NOTHING Works Anymore After Latest Update?!’ is closed to new replies.