bentracy

Thanks for the explanation, Alexandre! I installed your plugin and I’m seeing “WPRUS TEST – the plaintext password can be accessed and its length is 15” in the logs so that seems to be working successfully. My WPRUS logs also seem to indicate that everything else is supposedly successful. On my recipient site, I’m getting “successfully updated user” messages that include the [user_pass] => ** HIDDEN ** line along with “successfully logged in user” messages, yet it’s not automatically logging me in and the password doesn’t work. So odd. I think I’m just going to fall back on using the regular WP registration process but @laurajacob1986 I’d be curious to know if you end up finding a solution to your issue.

Hi again! I’ve heard back from Gravity Forms about this and their response explains why WPRUS is successfully syncing user data but password data is missing. Would you consider supporting the hooks mentioned in their response below?

For security, Gravity Forms does not save the password field value to the entry in plaintext, it is hashed using the WordPress core password hasher.

The add-on does use the WordPress wp_create_user, wp_update_user, and update_user_meta functions when creating/updating the users.

However, the WordPress functions for creating and updating users don’t support being passed a hashed password, it would hash them again, so the add-on doesn’t include the password when creating/updating the user.

After the add-on has created/updated the user, it then adds the hashed password directly to the user’s record in the wp_users table.

The password is then deleted from the entry.

The add-on does include hooks, gform_user_registered and gform_user_updated, so that other plugins can perform actions after it has created/updated the user.