This is really unnecessary. Twitter auto-shortens all URLs using their t.co shortener. All URLs may 'show' as the long URL, but they've been shortened automatically. Using your own short URL is only good for clarity when reading where the link goes, but not for making it easier to create longer tweets.Another thing for twitter, I am trying to keep the character count down so I have created an alias for www.911truthoutreach.org of 911to.org.
<meta name="twitter:card" content="summary" />
<meta name="twitter:site" content="@nytimesbits" />
<meta name="twitter:creator" content="@nickbilton" />
<meta property="og:url" content="http://bits.blogs.nytimes.com/2011/12/08/a-twitter-for-my-sister/" />
<meta property="og:title" content="A Twitter for My Sister" />
<meta property="og:description" content="In the early days, Twitter grew so quickly that it was almost impossible to add new features because engineers spent their time trying to keep the rocket ship from stalling." />
<meta property="og:image" content="http://graphics8.nytimes.com/images/2011/12/08/technology/bits-newtwitter/bits-newtwitter-tmagArticle.jpg" />
When you use the validator, if it passes, it should ask you to submit it so that the tags will actually be used in future tweets as the preview. If you don't see that option, all is good, it means you're probably already approved.First, I am not sure what it means to submit the site to twitter for approval. Is that the same as running a page through their Card Validator? Our Twitter App has been approved since December 18, 2014.
Nope. The validator is like Facebook's Open Graph tool. It's just to test the tags. Once you've submitted for approval, your whole domain will be approved and you'll never have to do that again.Also I would assume that I have to validate for every page that I want to have Tweeted. Is that correct?
I'm not sure at all what's causing that. Something on the server is preventing them from contacting your site. That's a problem that's likely outside of our ability to help.I am obviously missing something here: Should I ask twitter to determine the problem?
twitter:site is an optional tag. You can add it if you want, but it's not required.I noticed the HTML for the page I was validating that the twitter:site meta tag isn't present. Is this the one instance where the twitter meta tag has to be present?
Nice! That's new info to me. They used to explicitly ignore tags and only used their own. Good to hear they're playing nice now.Also Twitter does use the Open Graph og: tags in the event that there aren't the equivalent twitter:card tags.
Right now, we only support the summary card by default. You may be able to set a custom tag on specific pages for other card types, but I'd have to look into how to do that better.How do I indicate these cards for different types of content pages in JFBConnect?
I will have to wait and see if the correct image starts appearing in the tweets.When you use the validator, if it passes, it should ask you to submit it so that the tags will actually be used in future tweets as the preview. If you don't see that option, all is good, it means you're probably already approved.
This is really good to know, I was fearing that I would have to validate as part of the articles editing process.Nope. The validator is like Facebook's Open Graph tool. It's just to test the tags. Once you've submitted for approval, your whole domain will be approved and you'll never have to do that again.
I have been perusing the forums, and it seems the validator goes down from time to time, so maybe that is what I am experiencing. I asked Twitter if this was the case and I will let you know what they tell me when they get back to me.I'm not sure at all what's causing that. Something on the server is preventing them from contacting your site. That's a problem that's likely outside of our ability to help.
Thanks, since Twitter makes a big deal about this how would I add it other than manually?twitter:site is an optional tag. You can add it if you want, but it's not required.
I can't add another head tag so I will have to think about how to do that on a page by page basis. I see that as a major coding issue for you because you would have to add that as attribute to the plugin tag and an option in the module; adds another level of complexity.Right now, we only support the summary card by default. You may be able to set a custom tag on specific pages for other card types, but I'd have to look into how to do that better.
It's in our to-do list to allow adding custom Twitter Card tags just like we have support for Open Graph support. It's not been a highly requested feature though, so hasn't been a huge priority. Each type of Twitter Card (summary, photo, etc) needs to be approved for use on your site, which is more complex for users to go through as well.I can't add another head tag so I will have to think about how to do that on a page by page basis.
What happened when you tried to post to Twitter? What message did you get when you tried? Have you gone through the full channel setup and did you re-authenticate with the Twitter user and accept the "Can Post" permission on that login?I just posted to our channels and the post to Facebook was successful, but the post to twitter failed.
I have read twitter developer post where some people have been waiting months for each approval, unless you're Katie Perry or someone like that, then you get expedited.Each type of Twitter Card (summary, photo, etc) needs to be approved for use on your site, which is more complex for users to go through as well.
No I didn't re-authenticate.What happened when you tried to post to Twitter? What message did you get when you tried? Have you gone through the full channel setup and did you re-authenticate with the Twitter user and accept the "Can Post" permission on that login?
Join our newsletter to get alerts for Joomla releases, tips and tricks and extension updates.