You can get the actual permalink of tweet by using twitter user name and tweet id e.g https://twitter.com/chandanonline4u/status/499899357139697664
Hope this will help you.
No, I’m sorry, it does not 🙁
Retrieve the twitter user name id and tweet id as given:
$twitter_userid = get_option('itap_user_id');` // As mentioned in your plugin settings
$tweet_id = get_post_meta($post->ID, '_tweet_id', true);
Then create the tweet permalink:
$tweet_url = 'https://twitter.com/'. $twitter_userid .'/status/'. $tweet_id;
Now, it should solve your problem.
Yeah, I came as far as this 😉
But for whatever reason the tweet-ID isn’t part of the tweet-URL.
In the end i got it working on my own webspace, but not the client’s.
Well, now he wants it to work on his as well. I just tried it for about two hours. It just doesn’t work. It imports the tweet’s content just perfect, but the tweet-ID ist just some random number (not associated with any tweet).
Could this feature use some kind of server technology or something which may not be running on his server? His Server uses PHP5 and MySQL5.
Hi Simon!
It is sad that you still facing the same issue. This tweet id are some random numbers but this is what twitter API use as tweet id and gives us the same. For ref. https://dev.twitter.com/rest/reference/get/statuses/user_timeline
IF you get tweet url using tweet id and being redirected to some other tweet. It may be the twitter application issue. Check twitter application permission and generate new access token and trying using that.
Let me know if this works for you. Share the code and twitter username you are using to get twitter url.
No, the tweet-ID really is just random and doesn’t link to any tweet. I just get 404 on twitter with those IDs.
And my code is exactly the same as yours a view posts above.
I completely wiped the databse and made a whole new wordpress installation. Nothing. It must have to do with the server …
Are tweets getting imported from twitter? I can’t say anything about server issue. Try generating new access token and check twitter app permission.
Renewed the access tokes, nothing, tried it with a different twitter account, nothing.
I even tried it on a third server now, doesn’t work as well.
So it has to have something to do with the server configuration. I’m still in contact with the support from one of my hosts. I keep you updated.
Some servers block CURL and Cronjobs initially that may be the issue.
Cronjobs can’t be the problem as I get the tweets’ contents, i guess. But what does CURL do?
It was just for example not used here. Are you getting the right tweet id and link on local system setup?
I have no idea why you are getting this issue.
