You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Connection: supported deletion of a local user without a current user token
#52602
In the installed Manager code, deleted_user invokes disconnect_user_force(), then disconnect_user($id, true, true). unlink_user_from_wpcom() sends jetpack.unlink_user(local_user_id) using site authentication before checking the individual user token.
The case is an ordinary local customer, not the connection owner, with no current individual token. Past WordPress.com associations are unknown; absence of a token is not evidence that there was never an association.
Could a maintainer clarify the expected server-side effect when no association exists, and when an old association exists? What supported procedure should delete only this local customer while preserving the site connection and other users, including handling a network failure? Please point to official documentation or code defining these conditions and effects.
I searched issues and discussions for unlink_user; the historical change #2221 addresses unlinking deleted users but does not establish the current no-token case. This is a behavior/documentation question, not a demonstrated site-disconnection bug.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Self-hosted WordPress 7.1.1, WooCommerce 11.1.1, bundled
automattic/jetpack-connection6.19.2.In the installed Manager code,
deleted_userinvokesdisconnect_user_force(), thendisconnect_user($id, true, true).unlink_user_from_wpcom()sendsjetpack.unlink_user(local_user_id)using site authentication before checking the individual user token.The case is an ordinary local customer, not the connection owner, with no current individual token. Past WordPress.com associations are unknown; absence of a token is not evidence that there was never an association.
Could a maintainer clarify the expected server-side effect when no association exists, and when an old association exists? What supported procedure should delete only this local customer while preserving the site connection and other users, including handling a network failure? Please point to official documentation or code defining these conditions and effects.
I searched issues and discussions for
unlink_user; the historical change #2221 addresses unlinking deleted users but does not establish the current no-token case. This is a behavior/documentation question, not a demonstrated site-disconnection bug.All reactions