You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the docs and connecting Twitter, when trying to post, the following error message shows:
{
"errors": [
{
"message": "You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product",
"code": 453
}
]
}
All access levels and permissions have been checked. Read and write permission has been granted through the Twitter/X Developer portal.
Steps to reproduce
Follow the docs to connect to Twitter/X
Try to post an entry to Twitter/X
Craft CMS version
3.9.10
Plugin version
2.3.4
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered:
Looks like we're still using the v1.1 endpoints for Twitter for Craft 3.x and Social Poster 2.x. I believe this is addressed in Social Poster 3.x for Craft 4 and above.
I'll see what I can do about updating this, but as our Craft 3 plugins are heading towards their end of support soon-ish, a change this large isn't something we've been planning.
Describe the bug
After following the docs and connecting Twitter, when trying to post, the following error message shows:
{
"errors": [
{
"message": "You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product",
"code": 453
}
]
}
All access levels and permissions have been checked. Read and write permission has been granted through the Twitter/X Developer portal.
Steps to reproduce
Craft CMS version
3.9.10
Plugin version
2.3.4
Multi-site?
No
Additional context
No response
The text was updated successfully, but these errors were encountered: