Log in | Register
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. SCTwitterShare Easy Tag Not Working

Topic-icon SCTwitterShare Easy Tag Not Working

Active Subscriptions:

None
8 years 2 months ago - 8 years 2 months ago #57105 by webdevtim
SCTwitterShare Easy Tag Not Working, I am getting a Facebook share dialogue box instead of a Twitter Tweet dialogue box.

Below is the SCTwitterShare tag I am using. If I use the SCTwitterTweet I still get the Facebook share dialogue box. What I am missing here.
{SCTwitterShare href=http://911to.org/memorial-in-melbourn/ text=Honor America Inc’s Liberty Bell Memorial Museum in Florida, received an I-beam from the World Trade Center that was “twisted like taffy…” data_count=horizontal via=911TruthOut related=ae911truth,911Blogger,911truth_org,DC911truth,Davis911Truth,Anon911Truth,vernon911truth,911dokumentar,Seek911Truth hashtags=911truth,911truthoutreach,truthoutreachinc,wtc,wtc7,rethink911,sept11,NIST,FalseFlag,NeverForget  size=large dnt=true}

I am also using the following OpenGraph tags:
{JFBCAction id=2 text=Recommend}{SCOpenGraph image=https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg}{SCOpenGraph url=http://911to.org/memorial-in-melbourn/}{SCOpenGraph title=Installation of a 9/11 “Memorial” in Melbourne FL}
Last edit: 8 years 2 months ago by webdevtim.
The topic has been locked.
Support Specialist
8 years 2 months ago #57110 by mel
Could you try removing the quotation marks in the text field?
The topic has been locked.
Active Subscriptions:

None
8 years 2 months ago - 8 years 2 months ago #57116 by webdevtim
Thanks Mel, it didn't make any difference. Here are the tags that show up in "View Source" see: 911to.org/memorial-in-melbourn/ 
{SCOpenGraph image=https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg}

<meta property="og:image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/>
<meta name="image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/>
<meta name="twitter:image" content="https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg"/>
<meta property="og:image" content="https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg"/>
<meta property="og:url" content="http://911to.org/memorial-in-melbourn/"/>
<meta name="twitter:title" content="Installation of a 9/11 Memorial in Melbourne FL"/>
<meta property="og:title" content="Installation of a 9/11 Memorial in Melbourne FL"/>
<meta name="twitter:description" content="One of the most recent 9/11 memorials to receive a piece of steel from the World Trade Center was Honor America Inc’s Liberty Bell Memorial Museum in Melbourne, FL. The steel piece is an I-beam…"/>
<meta property="og:description" content="One of the most recent 9/11 memorials to receive a piece of steel from the World Trade Center was Honor America Inc’s Liberty Bell Memorial Museum in Melbourne, FL. The steel piece is an I-beam…"/>
<meta name="twitter:card" content="summary_large_image"/>
<meta property="og:type" content="article"/>
<meta property="og:site_name" content="9/11 Truth Outreach"/>
<meta property="fb:app_id" content="403004776514669"/>
<meta property="og:locale" content="en_gb"/>

You will notice that the Twitter:description isn't the same as {SCTwitterShare text=Honor America Inc’s Liberty Bell Memorial Museum in Florida, received an I-beam from the World Trade Center that was twisted like taffy…} as used in the tag.

I got this error from the Facebook Object Debugger: Errors That Must Be Fixed - Circular Redirect Path - Circular redirect path detected (see 'Redirect Path' section for details).

I think the solution lies here: K2 adds in the header:
<link href="/557-news-releases/472-installation-of-a-9-11-memorial-in-melbourne-fl.html" rel="canonical"/>
but the og:url property is:
<meta property="og:url" content="http://911to.org/memorial-in-melbourn/"/>
which Facebook sets as the cannonical URL for the page, but this redirects to:
<link href="/557-news-releases/472-installation-of-a-9-11-memorial-in-melbourne-fl.html" />
Which is the canonical URL for the page as set in the page header. So there are essentially two canonical URLs for the page and Facebook is getting confused.

Also the JWPlayer Social Share feature was interfering with JFBConnect, so I turned the JWPlayer Social Share feature off. With it on, because there were videos on the page, the Facebook posts got treated as if they were videos, which threw an error on Facebook.
Last edit: 8 years 2 months ago by webdevtim.
The topic has been locked.
Active Subscriptions:

None
8 years 2 months ago #57120 by webdevtim
One problem solved, the JCE editor was making a link out of the href= property. Twitter icon now appears.
The topic has been locked.
Support Specialist
8 years 2 months ago #57124 by alzander
Can you tell us which issues still remain? I'm a bit confused as to what is, or isn't, working now.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
8 years 2 months ago - 8 years 2 months ago #57130 by webdevtim
OK,

1. I don't know where this is coming from. These are the K2 images generated in the article: 
<meta property="og:image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/> 
<meta name="image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/>
not the special Facebook images create top comply with the Facebook format, I don't need both in the header.
<meta property="og:image" content="https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg"/>

I got rid of it by disabling the Open Graph - K2 plugin and then it comes back anyway. Guess I have to comb through things more carefully to see what could be generating this.

2. Using this short URL, 911to.org/memorial-in-melbourn/, in the og:url property causes a problem in Facebook.
because Face book marks this as the canonical URL, but this is a re-direct that resolves to www.911truthoutreach.org/557-news-releas...in-melbourne-fl.html but this is designated as the canonical URL in in the page header. Just noticed that his is a relative link, but Facebook is picking it up as an absolute path. This is Facebook and I think I am just going to use the long URL and worry about this where Twitter is concerned unless you have a quick fix I can apply. One suggestion I tried was adding RewriteCond %{HTTP_USER_AGENT} !facebookexternalhit to ,htacces. The problem may also be that the short URL is not HTTPS.

Changing to the long URL resolves problem #2, though it didn't resolve the problem of using the short URL, but I am still getting a warning:

Meta with name instead of property
The meta tag on the page was specified with name 'author', which matches a configured property of this object type. It will be ignored unless specified with the meta property attribute instead of the meta name attribute.


3. The Twitter share button isn't generating any image: 
{SCTwitterShare href=http://911to.org/memorial-in-melbourn/ text=Honor America Inc's Liberty Bell Memorial Museum in Florida, received an I-beam from the World Trade Center that was twisted like taffy…; data_count=horizontal via=911TruthOut related=ae911truth,911Blogger,911truth_org,DC911truth,Davis911Truth,Anon911Truth,vernon911truth,911dokumentar,Seek911Truth hashtags=911truth,911truthoutreach,truthoutreachinc,wtc,wtc7,rethink911,sept11,NIST,FalseFlag,NeverForget  size=large dnt=true}
, when <meta name="twitter:image" content="www.911truthoutreach.org/images/socialme...-museum-banner.jpg"/> is clearly in the page header

What I am getting is:
Honor America Inc's Liberty Bell Memorial Museum in Florida, received an I-beam from the World Trade Center that was twisted like taffy…; http://911to.org/memorial-in-melbourn/ #911truth,#911truthoutreach,#truthoutreachinc,#wtc,#wtc7,#rethink911,#sept11,#NIST,#FalseFlag,#NeverForge via @911TruthOut
Which is 148 characters too long, so I guess I can only included 1 hashtag and that I have to pare the text down some more to get it to fit. But there is no image, and I am not sure how to get an image transferred, because I see no image properties for Twitter Share.

Possible solution:

Images referenced in a Card are also cached based on URL. This often causes images to not update when the above Card refresh technique is used.

To work-around this issue, you can add an extra parameter at the end of your image URL so that the Twitterbot treats the image as a unique URL and re-fetches the image.

For example:

<meta name="twitter:image" content="http://example.com/myimage.jpg?4362984378" />

This did the trick, #3 solved.
File Attachment:


Also Found this Alex:

Render a Tweet with JavaScript
Twitter’s widget JavaScript scans the page DOM on execution, converting blockquote.twitter-tweet elements into fully-rendered embedded Tweets based on element content.

Developers dynamically inserting new content into a page which may possibly contain embedded Tweet markup should pass the newly inserted page fragment to twttr.widgets.load() to initiate a new scan for embedded Tweet content.

Developers may directly insert a rendered embedded Tweet onto the page without a blockquote.twitter-tweet scan by passing Tweet, options, and a HTML element to twttr.widgets.createTweet().

Last edit: 8 years 2 months ago by webdevtim.
The topic has been locked.
Support Specialist
8 years 2 months ago #57143 by mel
#1.
<meta property="og:image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/> 
<meta name="image" content="https://www.911truthoutreach.org/media/k2/items/cache/4739b6c64144f72975550c5e8df1b948_M.jpg"/>
These first two tags are not coming from JFBConnect as they are not in the block that we insert. My guess is that they're coming from K2.
<meta property="og:image" content="https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg"/>
Please check to see if you have any defaults set in the JFBConnect backend > Open Graph > Configuration area.

#2.
Meta with name instead of property 
The meta tag on the page was specified with name 'author', which matches a configured property of this object type. It will be ignored unless specified with the meta property attribute instead of the meta name attribute.
K2 is inserting the author metatag. Facebook has the concept of author, but that warning states that it needs to be defined as the follows: <meta property="author" ... instead of <meta name="author"... With that being said, I believe that Facebook expects that value of the author to be a Facebook ID, not just text?

#3. Sounds as if this is solved?

Render a Tweet with JavaScript
Twitter’s widget JavaScript scans the page DOM on execution, converting blockquote.twitter-tweet elements into fully-rendered embedded Tweets based on element content.

Developers dynamically inserting new content into a page which may possibly contain embedded Tweet markup should pass the newly inserted page fragment to twttr.widgets.load() to initiate a new scan for embedded Tweet content.

Developers may directly insert a rendered embedded Tweet onto the page without a blockquote.twitter-tweet scan by passing Tweet, options, and a HTML element to twttr.widgets.createTweet().

Yes, this is a way of rendering a Tweet but we don't currently support this method of doing so.

-Melissa
The topic has been locked.
Active Subscriptions:

None
8 years 2 months ago #57147 by webdevtim
I am really getting tired of K2. No updates in year and a half and K2 3 has been promised to be released for 3 years now.

Social Media is very important and K2 should permit granular control over that and it doesn't. I shut all Social Media off in K2 parameters and still K2 inserts og: meta tags. I guess I will comb the code and find the routine that inserts the og: tags and just delete that section of code and code in any other file that depends on that section of code.
<meta property="og:image" content="https://www.911truthoutreach.org/images/socialmedia/facebook/liberty-bell-memorial-museum-banner.jpg"/>
This is what I want and what is added in the og: and twitter: tags in other words this is on purpose not something errant..

2. Using this short URL, 911to.org/memorial-in-melbourn/, in the og:url property causes a problem in Facebook.

I would still like to present short URLs in Facebook, but need to solve the circular reference problem. See previous discussion of this.

Render a Tweet with JavaScript
Twitter’s widget JavaScript scans the page DOM on execution, converting blockquote.twitter-tweet elements into fully-rendered embedded Tweets based on element content.

Developers dynamically inserting new content into a page which may possibly contain embedded Tweet markup should pass the newly inserted page fragment to twttr.widgets.load() to initiate a new scan for embedded Tweet content.

Developers may directly insert a rendered embedded Tweet onto the page without a blockquote.twitter-tweet scan by passing Tweet, options, and a HTML element to twttr.widgets.createTweet().

Please make this a priority for the next release of JFBConnect because this will really make tweets coming from JFBConnect websites really shine.

The last thing is that Reddit support would also be really nice in the next release.
The topic has been locked.
Support Specialist
8 years 2 months ago #57152 by alzander

I would still like to present short URLs in Facebook, but need to solve the circular reference problem. See previous discussion of this.

Yeah, that's going to cause an issue. The short URL redirects to the normal page, but then the main page uses an og:url of the short URL. It's a redirect loop and Facebook can't make heads or tails of where to look for the tags.

I don't know of any way that you can share a short URL that redirects elsewhere to use that in the display of a share.

Please make this a priority for the next release of JFBConnect because this will really make tweets coming from JFBConnect websites really shine.

I'm still not clear on what that feature is or how it works. Can you explain a little more? I found this code on the Embedded Tweet FAQ that mentions what you posted above, but can't really understand how it works:
dev.twitter.com/web/embedded-tweets

Also, just to note, we do have an embedded tweet Easy Tag you may want to try:
{SCTwitterOEmbed url=https://twitter.com/BarackObama/statuses/266031293945503744 maxwidth=550}

The last thing is that Reddit support would also be really nice in the next release.

It won't be in the next release, but we do have plans for more providers in a release later this year.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
8 years 2 months ago - 8 years 2 months ago #57154 by webdevtim

Yeah, that's going to cause an issue. The short URL redirects to the normal page, but then the main page uses an og:url of the short URL. It's a redirect loop and Facebook can't make heads or tails of where to look for the tags.
I don't know of any way that you can share a short URL that redirects elsewhere to use that in the display of a share.

Yeh I have been looking on SourceForge and tried most of the suggestions from there, a lot of people have run into this problem, but no joy. The only problem is that when I use the "Create Post" feature that the full URL gets sent along to twitter rather than the short URL. The problem with that is that because the first 24 characters of the link are involved with just the root and path to the Latest News category which is identical for every post from the News Articles.

I'm still not clear on what that feature is or how it works. Can you explain a little more? I found this code on the Embedded Tweet FAQ that mentions what you posted above, but can't really understand how it works:
dev.twitter.com/web/embedded-tweets
Also, just to note, we do have an embedded tweet Easy Tag you may want to try:

{SCTwitterOEmbed url=https://twitter.com/BarackObama/statuses/266031293945503744 maxwidth=550}

It looks like this is embedding exiting Tweets with a Tweet ID, not a way to have twitter construct a fully expanded tweet from the parameter list sent along.
I will look into it and get back to you in a week, as this will requires a little more thorough reading of the twitter API. but I might make a tweet to our twitter page and then copy the link from that and then use the Easy Tag you mention above.

It won't be in the next release, but we do have plans for more providers in a release later this year

I know this is a lot of work. Are you making enough off SourceCoast to make it worth your time?
Last edit: 8 years 2 months ago by webdevtim.
The topic has been locked.
  1. Forum
  3. Discontinued Products
  5. JFBConnect v8.x Support (Joomla 3 Only) (CLOSED)
  7. SCTwitterShare Easy Tag Not Working
From the Blog
Facebook | Twitter | LinkedIn | Blog RSS