-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught RuntimeException in wp-content/plugins/wp-to-twitter/vendor_prefixed/vendor/noweh/twitter-api-v2-php/src/Media.php:61
#16
Comments
Checking things in the XPoster Pro settings, I see the connection to X is set up but incorrectly configured
Either way, the exception should be caught by the plugin. |
Can you tell me what type of image you set as the featured image? |
Nothing special. The most recent post I published has https://www.bram.us/wordpress/wp-content/uploads/2024/12/AQ5RAHpMaM.jpg set as the featured image. It’s a thumbnail saved straight from YouTube. This used to work before X changed their API requirements. |
What version of XPoster Pro do you have? I haven't been able to reproduce this yet. The actual exception is happening in an upstream library, so I'd prefer to go in the direction of preventing the error. But |
Latest ones: XPoster 4.2.6 (noticed the update to 4.3.0 went out the other day) + XPoster Pro 3.0.0 |
So XPoster Pro 3.0.0 is very old; that was the terminal release of WP Tweets Pro. You'll want to switch over to XPoster Pro: https://xposterpro.com. I sent out an email to all active license holders at the time I made the switch to host Pro on a different website, but you may not have seen that. Use the discount code REBRAND2023 to get a 23% discount on the new account. All existing licenses administered through joedolson.com were cancelled in 2023. |
Describe the bug
Whenever the plugin tries to post something, it throws an exception
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Any OS
Smartphone (please complete the following information):
Any device
Additional context
Version info:
Stack Trace:
The text was updated successfully, but these errors were encountered: