jetpack
#1905 closed enhancement (wontfix)
Likes: do not require user to be logged into wp.com to like
| Reported by: |
tomdryan
|
Owned by: |
tmoorewp
|
|---|---|---|---|
| Priority: | low | Severity: | minor |
| Plugin: | jetpack | Keywords: | Likes |
| Cc: | jeremy+wp@… |
Description
If the Jetpack "like" button is enabled and the user is not currently logged into wp.com, it will display a very generic looking login dialog box without any explanation, which is very confusing to most users. What are they logging in to the self hosted site or something else?
Very simple solution: Allow the admin to configure their site so the "like" button is not displayed when a user is not logged in to wp.com
More complete solution:
- If the user is not logged in to wp.com, then allow them to still "like" the post and display on the self hosted site as "liked", but have it just saved on the self hosted site and not sent to wp.com.
- Create a wp connect plugin that allows self hosted sites to check with wp.com via an API and give users the option of connect with their wp.com accounts (even if they retain their local login).
- If the user chooses to connect their self hosted user account to wp.com, then the self hosted site can start sending all archived "likes" and future "likes" back to wp.com
I'm really excited about the "like" functionality of Jetpack, but it is a little too rough around the edges at this point on self-hosed sites. This enhancement would go a long way to making it seamless.
Change History (5)
#1
@
11 years ago
- Cc jeremy+wp@… added
- Keywords Likes added
- Priority changed from normal to low
- Severity changed from normal to minor
- Summary changed from Jetpack "Like" Button: Don't require user to be logged into wp.com to like to Likes: do not require user to be logged into wp.com to like
#3
@
11 years ago
- Resolution wontfix deleted
- Status changed from closed to reopened
tmoorewp: Did you actually read the description of the problem? If you want to require that someone be logged into WP.COM to like a post, than you should at least give the admin the option to hide the WP.COM like button if the user is not logged in.
It is very poorly done currently where if the user is not logged in to wp.com, they get a very generic login dialog with very little info about what it is that they are supposed to be doing. Note that they already may be logged into the the site that they are viewing so that it is very confusing to the user to be asked to be logged in again. This is a very poor interface and I provided several suggestions to fix it in the description.
The WordPress effort needs to pay a hell of a lot more attention to user experience than the current "Like" functionality provides.
#4
@
11 years ago
- Resolution set to wontfix
- Status changed from reopened to closed
The issue has been passed along. Since Likes are a part of WordPress.com, the issue needs to be addressed there, not in Jetpack. Thank you for your feedback and concern.
#5
@
11 years ago
Isn't the purpose of JetPack to "fill in" the functionality on self hosted sites that is provided by WP.COM? This would not be an issue on the wp.com side because either everyone on that side is already logged in, or if they need to log in, it would make perfect sense to pop up the wp.com login info. This makes no sense on a self hosted site.
I'm happy to take it up with the powers that be at wp.com. Could you provide the ticket # where you "passed this issue along" to them?
Likes are tied into the WordPress.com cloud services, so being logged into a WordPress.com cloud is required.