Why no Twitter (X)?

  • Resolved jamminjames

    (@jamminjames)


    1 month, 3 weeks ago

    Why no is there no Twitter (X) connection option in Jetpack Social? It’s great that you include Bluesky, etc, but I’d think Twitter would be a no-brainer. Is there any way to add it (function hook, etc)?

Viewing 15 replies - 1 through 15 (of 28 total)
1 2
  • Plugin Support fujifika (a11n)

    (@fujifika)

    1 month, 3 weeks ago

    Hi @jamminjames ,

    Great question! Unfortunately, X (previously Twitter) is no longer available as a connection option in Jetpack Social. Back in 2023, X dramatically changed the terms and pricing of their API, and despite our attempts to negotiate, we weren’t able to reach an agreement. As a result, we had to discontinue the X integration.

    You can read more about what happened here: https://jetpack.com/resources/the-end-of-twitter-auto-sharing/

    We know it’s frustrating, X would indeed be a no-brainer to include.

    In the meantime, Jetpack Social still supports auto-sharing to Facebook, LinkedIn, Tumblr, Instagram, Mastodon, and Bluesky. For X, the workaround for now is to manually share your posts by pasting the link into a tweet.

    Hope that helps clarify things!

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    Ok, thanks. It’s not accepting my Mastodon handle. My profile is at https://mastodon.social/@humortimes, so the handle should be “@humortimes”, correct?

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    Also, when I try to share a previously published post (classic editor), I get:
    “An error occurred while sharing your post.”

    I can’t find anything in our server logs that might indicate the reason for the error. Tried deactivating all plugins except Jetpack & Jetpack Social and Classic Editor, no change. Also removed our child theme functions.php file and a couple mu-plugins we have, no change.

    How can we troubleshoot this? Thanks!

    Plugin Support fujifika (a11n)

    (@fujifika)

    1 month, 3 weeks ago

    Hi @jamminjames,

    Since you’re having more than one issue, I suspect there might be an issue with your Jetpack connection, and we’d love to take a closer look at it.

    Could you please post your site URL here so that we can take a look?

    If you want it to remain private, you can also contact us via this contact form.

    If you choose to reach out directly, please include a link to this thread.

    Thanks!

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    humortimes.com, thanks! Yes, it’s definitely the connection.

    We are using an mu-plugin for REST API hardening, but have provisions in it for Jetpack. The problem persists whether or not the mu-plugin is present. The script is here.

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    We also use Cloudflare CDN, but I’ve checked the rules that we have set up, and don’t think that’s the problem.

    Chatoxz (a11n)

    (@chatoxz)

    1 month, 3 weeks ago

    Hello there, Sebastian here. I hope you are doing well.

    Thank you for sharing additional details of these issue with us-.

    I reviewed your site and saw an issue where the Jetpack Connection fails because your server is sending a 503 error code. Jetpack needs this connection to function correctly for most of its features.
    A web server sends a 503 error code when you exceed its resource limits. This may mean that you need to upgrade your server.
     
    In any case, you should contact your hosting provider about this. They can investigate why this is happening on your server and offer suggestions for fixing it.

    You can find more details about Jetpack and how to fix Jetpack connection issues here:

    https://jetpack.com/support/getting-started-with-jetpack/fixing-jetpack-connection-issues/
     
    I recommend checking into this as soon as you can because your site’s visitors may occasionally have trouble accessing it.

    Regarding the script you share, helping with these level of customizatrion fall outside of our scope of support
     
    Let us know when you have resolved this, and we can test the Jetpack connection again.

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    Thanks, was able to find the problem in our Nginx settings. Now, I’m trying to re‑share posts. I can do it in the Classic Editor, but not with the Block Editor. In the documentation, it says:

    “Bring up the Jetpack menu by clicking the Jetpack in the top right corner.”

    However, there is no Jetpack link nor icon there. We have Yoast, so I see that icon, but not for Jetpack. Scrolling down the ‘Post’ column, I see nothing for Jetpack.

    One more question: Shares show title with link, plus image. This is great. How can we add author and/or anything else, like our company name?

    • This reply was modified 1 month, 3 weeks ago by jamminjames.
    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    Also, does Jetpack automatically install a Woocommerce mu-plugin? Since installing Jetpack, it keeps reappearing.

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 3 weeks ago

    I’ve got it set up and not seeing errors, log shows some posts sent, however, checking my socials, they were not in fact posted.

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 2 weeks ago

    After trying for hours to diagnose this issue with the help of Copilot, it suggested posting a support request with Jetpack, telling them:

    “My Jetpack connection is stuck in a ghost state.

    Locally, Jetpack is fully disconnected and reconnected cleanly, but
    test__wpcom_connection_test fails and WordPress.com still shows the site
    as connected… Please purge the Jetpack connection for site ID xxxxxx”

    I did that, guess we’ll see what happens.

    Plugin Support Alin (a11n)

    (@alinclamba)

    1 month, 2 weeks ago

    Hi @jamminjames,

    Thanks for all the detailed testing and for your patience so far. At this point, we can narrow everything down to one core issue.

    Right now, the Jetpack connection can’t fully establish because access to xmlrpc.php on your site is being blocked or modified. Until that’s resolved, Jetpack won’t be able to complete its connection handshake, and features that depend on the connection, like Social sharing and the Jetpack panel in the Block Editor, won’t work reliably.

    A simple way to verify this, without any command-line tools, is to check the XML-RPC endpoint directly in your browser:

    https://www.humortimes.com/xmlrpc.php?for=jetpack

    When XML-RPC is working correctly, that URL should return a plain XML response. If it shows a blank page or regular HTML output, it means something upstream is still interfering with access to xmlrpc.php.

    From what we’re seeing so far, something at the server or CDN level is blocking or altering that endpoint. Since you mentioned Cloudflare earlier, this is a common place where XML-RPC can be affected by security rules or optimizations.

    This guide may be helpful as you investigate further on that side:

    https://jetpack.com/support/getting-started-with-jetpack/configure-jetpack-cloudflare/

    Jetpack relies on xmlrpc.php to communicate with your site, and certain Cloudflare settings, such as WAF rules, bot protection, or response transformations, can interfere with that communication. Jetpack support can’t adjust Cloudflare configuration directly, but once XML-RPC responds correctly, the Jetpack connection should be able to complete normally.

    For now, the best next step is to focus on getting that XML-RPC endpoint responding correctly. After that, we can recheck the Jetpack connection and then look again at Mastodon or any remaining Social issues if they still persist.

    Let us know once that endpoint is accessible and we’ll be happy to continue from there.

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 2 weeks ago

    Silly me, our Really Simple Security plugin had ‘disable xml-php’ set to on. Now working, including Mastodon and Jetpack icon in Block editor.

    Still curious, does Jetpack install the mu-plugin, woocommerce-analytics-proxy-speed-module.php? It keeps installing itself since we started using Jetpack.

    Also: Our shares show title with link, plus image. This is great. How can we add author and/or anything else, like our company name?

    • This reply was modified 1 month, 2 weeks ago by jamminjames.
    Thread Starter jamminjames

    (@jamminjames)

    1 month, 2 weeks ago

    A couple other questions, the shares show the first part of the article, instead of the excerpt (set with Yoast). Can that be changed? Also, I’ve seen conflicting info on this: Is it possible to install Jetpack Social as a stand alone plugin, without the main Jetpack plugin?

    Thread Starter jamminjames

    (@jamminjames)

    1 month, 2 weeks ago

    I thought everything was working now, but I guess not. Re-share seems to work, however, the newly published posts are not making it to the social platforms. After publishing a notice says:

    “Post published and sharing on LinkedIn (Humor Times), Mastodon (@[email protected]), Instagram (Humor Times), Threads (humor_times_pub).”

    However, they are not there.

Viewing 15 replies - 1 through 15 (of 28 total)
1 2

You must be logged in to reply to this topic.