Quote:
Originally Posted by BirdOPrey5
If you reload the page does the tweet show?
|
Hey, thanks for the response. No, no change when you reload. Remains a blank post, but I can see the JS code there in a View Source. That may be noteworthy insofar as loading that oEmbed link directly (the target result of the replacement) returns all of the data (and a render script) as below (this is Twitter's example of it in practice):
https://api.twitter.com/1/statuses/o...40144317198338
So it's like it's not functioning as a GET, or not writing/parsing/embedding the response. I'm just not sure. Then again, it probably wouldn't show the response in the View Source even if it was working -- nevermind, just sorted that out.
Obviously I'm at a bit of a loss.
Also, I'm wondering about how safe/secure this is even if I did make it work. I suppose I'm only letting people pass a numeric string through to the script itself, so it can't get loaded up with anything malicious. See any issues on that front (as a secondary question)? Probably a non-issue, but I thought I'd ask someone who actually has a clue (unlike myself).