bamajr

@claudeschlesser

I understand the security issue related to the social network accounts as it relates to an email address and can appreciate the security issues that can come up as a result of trying to link social accounts with WordPress accounts.

However, in the case of Twitter, LinkedIn and WordPress the email address used for each account must be verified before an account can be created, so why does this not pull across when connecting with your plugin?

For Instance…

I have Facebook, Twitter, Google, LinkedIn and WordPress.com accounts set up. All of those accounts use the same email address I use for my WordPress website (https://bamajr.com/). With all these accounts, except Google (which works fine), I even have the same username (bamajr) and I use the same First/Last name.

When I log into my WordPress website using your plugin and my Facebook/Google credentials, I’m matched with the correct profile, previously created, on my WordPress website.

When I log into my WordPress website using your plugin and my Twitter, LinkedIn and/or WordPress credentials, I’m not even able to get to the dashboard nor see my user profile. If I try, I get “You do not have sufficient permissions to access this page.” If I then log out of my WordPress website and log back in with Facebook/Google, or even the account I previously used without your plugin, there are users created with really long (hash-like) email addresses and no first/last name.

It seems to me if my WordPress website, Facebook, Twitter, Google, LinkedIn and WordPress.com accounts are all using the same email address, username and first/last name, then I should be directed to the correct user profile when logging in with your plugin. Otherwise, what is the point in matching user profiles in a WordPress web site with those of social networks?

And again I ask, if it works correctly with Facebook/Google, why isn’t it working for Twitter, LinkedIn and WordPress, given the information I’ve provided in this reply?

RE: Login Email Sync Issue…

The plugin is supposed to “SYNC” the username and email address for the purposes of logging in, but is not supposed to replace a username with an email address. Its supposed to allow a person to log in with either one.

However, I have been able to do further testing and prove it is unrelated to your plugin and have notified the plugin developer as such.

The only reason it only came to light when configuring your plugin, is that a user logged in to my WordPress website with social credentials (I.E. Facebook/Google). They went to their user profile on my WordPress website to make sure nothing had changed within the profile. Instead of exiting the profile they clicked the “Save” button. This is actually where the issue is. A user can use both username and email address, with the “Login Email Sync” plugin, until they update/save their user profile. Then they can only log in with email addresss.

Oh, and FYI, when users update their profile while logged in with a Facebook or Google account, this plugin is causing the “Login Email Sync” plugin to permanently change the username field to be the user’s email address, so that their username is no longer available. So, going forward, that person is required to log in with an email address, unless they log in with a Facebook/Google account.

This does not happen when the “Login Email Sync” plugin is installed and this plugin is not.

I don’t know how in the world I’m going to fix this issue. I do not want to force users to log in with their email address, if they already have a username/password set up on my site. The ability to log in with their credentials from other social sites is supposed to be a convenience to my websites visitors, not screw up the site entirely.

Terrible goof.

I agree…

This plugin is awesome by itself, but is stronger with Akismet. I have often wondered why WordPress didn’t do something similar, with their Akismet plugin, to begin with.

Okay… So I’m not sure what is going on…

The issues in my last three posts, seem to have fixed themselves, with a hard reset of the server. I cannot explain why, as I said before, there was no configuration change to the servers.

Oh well, for the time being, it is up and running.

I tried to disable and delete the Jetpack plugin, so I could re-install it, but I can’t get a connection, through my https://bamajr.com WordPress blog to the WordPress plugins now either.

Oh… FYI, Akismet now also gives an error:

The key below was previously validated but a connection to akismet.com can not be established at this time. Please check your server configuration.

Again, as of just a few minutes ago, these were all working.

No changes to server. No changes to WordPress installation.

What the heck is going on?

I just got the “We were unable to get your stats just now. Please try again.” error today. It just started.

The JetPack plugin and stats have all been working just fine on https://bamajr.com, until just a few minutes ago. It is a self hosted web site and I haven’t done anything except write new blog posts.

I’m using Jetpack by WordPress.com, Version 1.2.2 on WordPress 3.3.1

It has worked, without issue, since I initially installed it. I have updated WordPress and the Jetpack plugin, since the installation, and it continued to work. Then, all of a sudden, today, it quite.

I tried the “Disconnect” option, to disconnect from WordPress.com, but now when I click the “Connect to WordPress.com” button, I get another error:

Jetpack could not contact WordPress.com: register_http_request_failed. This usually means something is incorrectly configured on your web host. Could not open handle for fopen() to https://jetpack.wordpress.com/jetpack.register/1/

I’m the host, and nothing has changed on the server, so I’m not sure what is going on.

Okay, so where does the information displayed here:

Requires WordPress Version: 3.0 or higher
Compatible up to: 3.1.4
Last Updated: 2011-1-14
Downloads: 7,036,346

…come from?

Does the “Compatible up to:” area come from the readme.txt file or somewhere else?

If the plug-in is only advertising that it works up to 3.1.4, isn’t that giving people a mixed message about what versions of WordPress it will actually work with?

I find this weird and annoying. Some plug-in developers get this right, others do not.

I use a plugin called Better Plugin Compatibility Control which supposedly uses a mix of the voting area and the readme.txt file, yet they don’t even updated their own plug-in correctly.

I posted this same issue for them here: Better Plugin Compatibility Control

It is odd to me how some plug-in developers have no problem with this, but many (I’d go as far as saying most) do.

As far as I know the “Compatible up to:” section…

Requires WordPress Version: 2.9 or higher
Compatible up to: 3.2.1
Last Updated: 2011-7-12
Downloads: 4,316,084

directly above the rating system, has nothing to do with the “Broken” or “Works” voting area…

9 people say it works.
10 people say it's broken.

As far as I’m aware, the “Compatible up to:” area is where the developer advertises which versions of WordPress their plug-in will work with, because 10 people say Contact Form 7 is broken when used in WordPress 3.2.1 and only 9 say it will work.

You are referring to the “Compatibility” box…

4 people say it works.
3 people say it's broken.

where users vote for “Broken” or “Works” and I’m referring “Compatible up to:” section…

Requires WordPress Version: 3.0 or higher
Compatible up to: 3.2.1
Last Updated: 2011-7-7
Downloads: 1,225,405

directly above the rating system. As far as I’m aware, that area is where the developer advertises which versions of WordPress their plug-in will work with.

The readme.txt file still missing with the latest version of WordPress.

This plugin continues to be packaged with the WordPress installations, but doesn’t follow WordPress’ own suggestions to have a readme.txt file with the plugin.

Where is the following located, if not in the readme.txt file?

Requires at least: ?.?
Tested up to: ?.?
Stable tag: ?.?

The Better Plugin Compatibility Control plug-in does not specify that it has been tested in version 3.2.1 in the readme.txt file.

Requires at least: 2.8
Tested up to: 3.2

Has it or hasn’t it?

If it has, why is the “Tested up to:” line only reflecting version 3.2?

Kinda funny that this plugin is identifying it’s own flaw.

I’m pretty sure the idea behind “-webkit-text-size-adjust” is to be used in a separate CSS file, specifically for mobile devices.

Same goes for -webkit-box-shadow

But neither of them actually show up as approved/valid CSS for either CSS2.1, CSS3 or CSS Mobile.

According to the W3C “-webkit-text-size-adjust” doesn’t exist in any approved model of CSS 2.1 or 3.