Dharmesh Patel

Hi @justinwyllie,

Thank you for reaching out to us and reporting this issue.

Yes, the plugin currently has a hardcoded limit of 280 characters. I have opened an issue on our GitHub repository regarding this, and we will aim to implement and release a fix in upcoming plugin releases. Please follow the GitHub issue to stay updated on its progress.

Feel free to reach out to us if you need help with anything else.

Thank you!

Hi @justinwyllie,

Thank you for reaching out to us.

Yes, that is the expected behavior. We currently have an open issue to add the ability to customize the order of the tweet text, hashtags, and link. In the meantime, you can use the autoshare_for_twitter_body filter to modify the tweet body according to your requirements. (You can find a code snippet for it here)

Please feel free to let us know if you need any further information.

Thank you.

Hi @behandlung,

Thanks for reaching out to us.

You can define the content to be shared at the post level by adding content to the “Custom message” field. However, we currently don’t have a UI for setting the default share content. We have an open issue for this, but there is no scheduled timeline for adding it to the plugin.

For now, you can use the autoshare_for_twitter_body filter to tweak the tweet body content to be shared. For example, if you want to share the post excerpt, you can use the following code snippet to do that:

add_filter(

    'autoshare_for_twitter_body',

    function( $tweet_body, $post ) {

        // Bail if we have a custom message.

        $custom_message = get_post_meta( $post->ID, 'autoshare_tweet-body', true );

        if ( ! empty( $custom_message ) ) {

            return $tweet_body;

        }

        // If we have an excerpt, use that.
    
        $excerpt = get_the_excerpt( $post );

        if ( ! empty( $excerpt ) ) {

            $tweet_body = $excerpt;

        }

        return $tweet_body;

    },

    10,

    2

);

Hope this helps you.

Thank you.

Hi @0283tubasa,

Thanks for the reaching out to us.

Could you please ensure that the “Post to X/Twitter when published” toggle is enabled when you published the post??Also, could you please manually attempt to post to X by clicking “Post to X/Twitter” and provide the details of any error you encounter?

Providing error details will assist us in identifying the root cause and resolving the issue.

Thank you.

Hi @ibiza69,

Apologies for the delayed response. We have fixed the issue with autoposting in version 2.2.0, and it has just been released. Please let me know if you are still facing any issues after updating the plugin, and we will be more than happy to help you with that.

Thanks

Hi @murilloferrari,

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.

Hi @ibiza69,

Thank you for reaching out to us.

Company published a job offer, today and is now show to public at our site:

Could you please provide more information on job publish process? is it automated? like publish through API etc…? If you are publishing post from wp-admin dashboard directly, could you please provide screencast of publish process? providing these information will help us to understand the issue you are facing.

Thank you.

Hi @peterdredd,

Thank you for reaching out to us.

This plugin relies on the Twitter API to facilitate the automatic sharing of your blog posts, It’s essential to note that Twitter imposes usage limits on its API. With Twitter’s Free API access, you are allowed?1,500 Tweets per month?and?50 requests within a 24-hour period. Exceeding these limits will result in receiving a “429: Too Many Requests” error from the Twitter API.

To ensure compliance with Twitter’s policies and to accommodate your needs if they exceed the Free API limits, we recommend considering a subscription to either the Basic or Pro access level. These access levels provide increased quotas and additional benefits to accommodate your needs. You can find detailed information on Twitter API access levels by visiting this link:?https://developer.twitter.com/en/products/twitter-api.

Best regards

Hello @ibiza69,

Thank you for getting in touch with us.

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:

1. Editor: Are you using the Block editor or the Classic editor?
2. 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.
3. 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.

Thank you.

Hi @salromano ,

Thanks for reaching out to us.

As mentioned here in the FAQ, the “429: Too Many Requests” error indicates that you have exceeded the usage limits of Twitter’s Free API access. With the Free API, you are allowed?1,500 Tweets per month?and?50 requests within a 24-hour period. Since you have surpassed the daily limit, we kindly advise waiting for 24 hours before attempting to tweet again.

To avoid encountering this error in the future and to have higher usage limits, we recommend considering a subscription to either the Basic or Pro access level. These access levels provide increased quotas and additional benefits to accommodate your needs. For more information on Twitter API access levels, you can visit this link: https://developer.twitter.com/en/products/twitter-api.

Best regards

Hi @chrisdca,

I’ve sent you the Site Health info separately.

Please provide the information on where did you sent it?

Thanks

Updates:
Error handling has been improved in the recent release 2.1.0 to provide more informative error messages. The plugin now offers clear error messages in case of failure.

Hi @chrisdca,

Thank you for reaching out to us.

Could you please provide more information about the issue you are facing?

• Is Autoshare displaying an error when scheduled posts are published? If yes, could you provide more details about the error?
• Could you also share a Site Health Info export from your site? This will help us replicate your setup and identify the issue.

Best regards,

Hi @visionrz,

Thank you for getting in touch with us.

Yes, Autoshare for Twitter works with custom post types. Therefore, you can enable Autoshare for Twitter for WooCommerce products through the settings, and you will be all set.

If you encounter any issues during the setup process, please don’t hesitate to contact us.

Best regards,

Hi @megazip,

Thank you for reaching out to us.

Yes, earlier we had 4 fields of Twitter connection settings. However, in the recent release (2.1.0), we have added support for multiple Twitter account connections, reducing the settings to only 2 fields, with other aspects being handled through the Twitter account connection UI. Unfortunately, we missed removing these last 2 lines of setup instructions. Could you please ignore them and proceed by clicking on “Save changes”?

We have already removed the unnecessary lines and fixed the instructions and it will be released in the next release.

We appreciate your feedback. Since this issue has already been addressed, I will resolve this issue. If you encounter any other issues, please feel free to open a new one.

Thanks!