Are you using Jetpack’s publicize feature on your site?
Recently while browsing through Facebook, we found several folks sharing links where WordPress replaced the site domain. Along with that, the status also read like this: Michelle Schulp published an article in WordPress.
<img class=”alignnone size-full wp-image-25095″ title=”Facebook Status being hijacked by JetPack publicize” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/fbstatusjetpackpublicize.jpg” alt=”Facebook Status being hijacked by JetPack publicize” width=”520″ height=”479″ />
This was alarming, so we decided to investigate the issue.
When you click on the link, it takes you the website. However when you click on WordPress, it takes you to a WordPress.com signup page on Facebook.
<img class=”alignnone size-full wp-image-25087″ title=”Landing page for WordPress.com’s app” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/wordpresscom-app.png” alt=”Landing page for WordPress.com’s app” width=”520″ height=”286″ />
We looked further to see if these sites were hosted on WordPress.com, a blog hosting service. Most of them weren’t. (see the <a title=”Self Hosted WordPress.org vs. Free WordPress.com [Infograph]” href=”http://www.wpbeginner.com/beginners-guide/self-hosted-wordpress-org-vs-free-wordpress-com-infograph/”>difference between free WordPress.com vs self-hosted WordPress.org</a>)
However, they all had one thing in common. All of them were using the Jetpack plugin which is created by the parent company of WordPress.com, Automattic.
In order to verify our findings, we decided to install Jetpack on a test site. We replicated the issue, and it is connected with the publicize feature of the plugin.
When setting up the publicize feature, you are asked to connect with Facebook and grant several permissions.
<img class=”alignnone size-full wp-image-25082″ title=”Facebook permissions for using Publicize feature in JetPack” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/facebook-permissions.png” alt=”Facebook permissions for using Publicize feature in JetPack” width=”520″ height=”390″ />
<img class=”alignnone size-full wp-image-25083″ title=”Allowing WordPress.com to post on Facebook for you” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/post-to-fb.png” alt=”Allowing WordPress.com to post on Facebook for you” width=”520″ height=”367″ />
During the permission process, you see the blue W logo instead of the grey W logo. How is that different?
Well, one is for WordPress.com (the blog hosting service) and the other is for WordPress.org (the software that we all come to love and use).
Confusing isn’t it.
Often beginners do not know the difference, so they think they’re really authorizing their WordPress site, not a third-party WordPress.com platform (see <a title=”How are WordPress.com and WordPress.org Related?” href=”http://www.wpbeginner.com/beginners-guide/how-are-wordpress-com-and-wordpress-org-related/”>the relations and differences</a>)
Furthermore, the wording through out the process does not make it clear that you’re authorizing WordPress.com rather than your actual site. See the confirmation screenshot below:
<img class=”alignnone size-full wp-image-25084″ title=”Connected to Facebook” src=”http://cdn.wpbeginner.com/wp-content/uploads/2014/12/connected-to-fb.png” alt=”Connected to Facebook” width=”520″ height=”293″ />
Now if you want publicize to do what it’s suppose to (automatically share your post when its published), this is what your users will see.
<img class=”alignnone size-full wp-image-25089″ title=”A Post shared on Facebook using JetPack’s publicize module” src=”http://cdn2.wpbeginner.com/wp-content/uploads/2014/12/shared-post-fb1.png” alt=”A Post shared on Facebook using JetPack’s publicize module” width=”520″ height=”307″ />
We did some further research to find that it’s not a new problem. It has been<a title=”Support thread about Publicize” href=”http://en.forums.wordpress.com/topic/why-does-my-custom-publicize-message-say-published-an-article-on-facebook#post-1571896″ target=”_blank” rel=”nofollow”>reported</a> <a title=”Published an article on WordPres, why not my website name ?” href=”http://en.forums.wordpress.com/topic/published-an-article-on-wordpress-why-not-my-website-name” target=”_blank” rel=”nofollow”>several</a> <a title=”Vikas published an article on WordPress, but I published on waystoworld.com” href=”http://en.forums.wordpress.com/topic/vikas-published-an-article-on-wordpress-but-i-published-on-waystoworldcom” target=”_blank” rel=”nofollow”>times</a> since 2013.
Considering Jetpack is auto-installed and auto-activated on several major<a title=”WordPress Hosting Providers” href=”http://www.wpbeginner.com/wordpress-hosting/”>WordPress hosting providers</a> by default, this should be corrected to decrease the confusion between <a title=”Self Hosted WordPress.org vs. Free WordPress.com – Infographic” href=”http://www.wpbeginner.com/beginners-guide/self-hosted-wordpress-org-vs-free-wordpress-com-infograph/” target=”_blank”>WordPress.com vs self-hosted WordPress.org</a>.
While we understand that Facebook has it’s limitation, there are certain things that can and should be corrected to better inform users.
<del datetime=”2015-01-05T16:31:36+00:00″>First, in the link data below post title, it should actually show the user’s domain to promote their brand instead of showing WordPress.</del> As Jeremy from the Jetpack team pointed out in the comments below, this is not possible due to Facebook restrictions.
Second, the wording that says Syed Balkhi published an article on WordPress should be rephrased to clear confusion.
One of the user who reported the issue, offered a suggestion on wording: Vikas shared a link via Publicize instead of saying Vikas published an article on WordPress.
Another alternative could be: … shared a link via JetPack because that’s what is really going on.
Lastly, in the confirmation dialog, it should say “you have successfully connected Jetpack with Facebook” or “you have successfully connected your Facebook account with Jetpack”. [Update: <a title=”Jetpack Github ticket” href=”https://github.com/Automattic/jetpack/p**l/1476″ target=”_blank” rel=”nofollow”>Ticket #1476</a> created by Jeremy]
We hope these suggestions help improve the Jetpack Publicize experience for users.
<a title=”JetPack for WordPress” href=”http://jetpack.me/” target=”_blank” rel=”nofollow”><img class=”alignnone size-full wp-image-25174″ title=”Jetpack Image” src=”http://cdn.wpbeginner.com/wp-content/uploads/2015/01/jetpack1.jpg” alt=”Jetpack Image” width=”520″ height=”252″ /></a>
Jetpack is a great plugin for beginners who <a title=”How to Properly Move Your Blog from WordPress.com to WordPress.org” href=”http://www.wpbeginner.com/wp-tutorials/how-to-properly-move-your-blog-from-wordpress-com-to-wordpress-org/”>move from WordPress.com to WordPress.org</a> because it allows you to retain a lot of cool features of WordPress.com while giving you the power and freedom of WordPress.org.
Note: The goal of this post is not to start a flame w*r rather it is to encourage discussion and share our opinion with the community. We have tremendous respect and appreciation for Automattic and the work they’ve done.
If you liked this article, then please subscribe to our <a title=”WPBeginner on YouTube” href=”http://youtube.com/wpbeginner” target=”_blank” rel=”nofollow”>YouTube Channel</a> for WordPress video tutorials. You can also find us on <a title=”WPBeginner on Twitter” href=”http://twitter.com/wpbeginner” target=”_blank” rel=”nofollow”>Twitter</a> and <a title=”WPBginner on Google+” href=”https://plus.google.com/101634180904808003404/posts” target=”_blank” rel=”nofollow”>Google+</a>.
This Demo Content Brought to you by <a href=”http://momizat.com/” target=”_blank” rel=”dofollow”>Momizat Team</a>
<h2>this is tags and keywords : wordpress themes momizat Tutorial wordpress templates</h2>