https://developers.facebook.com/docs/sharing/reference/share-dialog VS https://developers.facebook.com/docs/plugins/share-button
In experimenting with both the FB.ui share dialog and using the fb:share-button / class="fb-share-button" I've noticed that using the FB.ui method does not offer sharing options (Share on your timeline, friends' timeline, etc) in the dialog and the og:description is not displayed on the FB post (yet it is in the post preview) and markup formatting for the display is different. It's obvious that both methods are using two different services:
FB.ui: .../v2.0/dialog/share... and Share Button: .../sharer/sharer.php?...
One would think that by leveraging the JavaScript SDK a developer would have more options to customize the sharing experience, but in my experience thus far, that doesn't seem to be case.
Yes, I've run my links through the linter, my open graph tags are set properly and I've added the "scrape=true" to my query string.
At the very least, I'd hope that the og:description would get displayed on a FB post by leveraging the SDK and that the formatting would be the same. Any validation of this behavior and workarounds?
Same problem here; plus the share count on the url is not updated if shared with the share dialog; it is if it's done using the share button.
pretty weird, a bug maybe?
Related
I want to make a viewpager which is just like latest facebook application.
and the problem is with tabs.
however i tried to make it, but i need icons with text in tabs and multiple fragments and layouts associated with it.
two issue occurred when i tried to develop.
1. I compromised with my UI, and tried putting static icons in it, but they don't change on selection and they don't even have badge like in facebook application.
2. when i put that code in my application which i have developed in demo app, it shows error and after researching i found that my application don't have an actionbar. so it was giving error after calling getActionBar.
please someone can provide any example or link to that which can help me.
You can refer to the official solution: http://developer.android.com/training/implementing-navigation/lateral.html
Or try this awsome lib: https://github.com/astuetz/PagerSlidingTabStrip
We've been noticing an increase in number of broken links on our sitecore website.
Some it is due to
User Training
Publishing Issues (linked page is not yet published)
Maybe content editor issues
It's been hard to verify some of these but sometimes the link might have the authoring page URL (which means someone didn't follow the SOP), sometimes they have a strange url like /shell/Content Editor/...
So we are trying to proactively fix these before the pages go live.
I had a couple ideas like writing a Handler that would look through all "Rich Text Fields" and looking for inconsistencies (like authoring server URL). Also using a crawler-type of validator could help us (http://home.snafu.de/tilman/xenulink.html#Description) but we were wondering what the community was doing to address this issue.
The "internal link checker" usually works well but doesn't detect many of this erroneous setups (as I believe it sees them as 'external links').
Your input is greatly appreciated!
If you have RichText fields and create internal links, your internal link looks like this in the HTML view: "a href="~/link.aspx?_id=EB3AD128E7BF4F3C9F3812F701D7724E&_z=z" and when you hover with your mouse over it, is show "/Sitecore/Shell/Controls/Rich Text Editor/" before the ~/link.aspx. This is normal behavior. This link is modified to a normal link during rendering of the RTE field.
However, be sure to use the Sitecore controls like to render these RTE fields and to render links. Also using sc:fld() in XSLT instead of sc:field() can create strange links because sc:fld is rendering the raw value of the field.
In all of the Sitecore projects I have been working on, I didn't have much issues with broken links.
There is a known bug with copy-pasting links from a rich text editor, where path info is appended to the link (generating the /shell/Content Editor/ stuff).
Sitecore have a fix for it here:
http://sdn.sitecore.net/Products/Sitecore%20V5/Sitecore%20CMS%206/ReleaseNotes/KnownIssues%20Recommended/Copying%20and%20pasting%20link%20in%20rt%20fields%20may%20break%20the%20link.aspx
I would suggest a new Validation Action added to the workflow command before the items are finalized. Then you could actively stop them from being published and give immediate feedback. If you're not using workflows, you could add a new item level validator, but those often get ignored in my experience -- too many false positives on the existing validators.
I'm setting up a sharer on my site pages, and i've found different links for using the sharer :
share.php
sharer.php
sharer/sharer.php
Which one is the right one to use ?
In the Facebook doc it says the second one, but only with the third was i able to share to a fan page (no linked profile).
Is there a difference between sharing on a profile or on a page ?
Thanks.
There is not much difference among them, it is just their looks and size that is changed using the property type.
I would strongly recommend against:
"The Share button has been deprecated in favor of the Like button, and will no longer be supported.
Please use the Like button whenever possible to drive maximum traffic to your apps."
So, instead of waking up with an nonfunctional share button, you'd be better off with a like button, or implementing a share button from scratch using the JS SDK.
Also, I can tell you for a fact that most of the people would share on their own wall rather than on a page.
The correct one to use is sharer/sharer.php
<a href="https://www.facebook.com/sharer/sharer.php?u=example.org" target="_blank">
Share on Facebook
</a>
https://developers.facebook.com/docs/reference/plugins/share-links/
Is there anyway to detect if the tab app is being loading in the new timeline or not? I got clients asking to upgrade my layout but not all of them have upgraded so it makes it hard to do that. If I had a way to detect this it would be perfect.
I managed to do that by looking for an album called "Cover Photos" on the album list of that page. Here's a sample:
http://graph.facebook.com/-page_id-/albums?fields=name
You don't need a token unless the page isn't published yet.
The problem with this approach is that some pages still don't have cover picture yet, but it's the minority.
It's awful that this thing is called "Like"-Box and there is no way to like, comment or share on an actual wallpost shown in the activity feed!
Is there a way to customize the Like-Box core so that these three little items are shown?
Would be great!
The only customization options are those found on the documentation page. You could build your own though using the Facebook graph API to pull a pages feed down and add like and share buttons.