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
We already hide the UI that the two-factor plugin adds to profile.php, but our custom UI also includes password/email, and those are still in wp-admin/buddypress/bbpress/etc.
there's a lot of settings on wp-admin/profile.php that should not be changed there, and in the case of WordCamp, will cause the WordPress.org user data to get out of sync with the database. #13 (comment)
If a setting exists in the custom wporg-two-factor UI, then it'd ideally be removed from wp-admin/buddypress/bbpress/etc profile editors, and replaced w/ a link to the 2FA settings screen
wp_user* database values on sites that share user tables (wordcamp, buddypress, others?) should also be replaced w/ a link to the w.org profile editor
We might need to delay this while #114 is still using wp-admin, before the custom UI is built.
The text was updated successfully, but these errors were encountered:
I've gone back and forth on this, the wp-admin profile page is not accessible by most users, but is still required for Application Passwords (As used by the PHPUnit Test Reporters).
It feels like a complete hack, but filters and blocking change attempts doesn't seem to be worth it, and I don't like the look of the code.. so.. I'm super temped to just deploy some Javascript to remove the fields we don't want changed, along with a big banner.. That's what has resulted in me making #54.
We already hide the UI that the
two-factor
plugin adds toprofile.php
, but our custom UI also includes password/email, and those are still in wp-admin/buddypress/bbpress/etc.wp_user*
database values on sites that share user tables (wordcamp, buddypress, others?) should also be replaced w/ a link to the w.org profile editorWe might need to delay this while #114 is still using wp-admin, before the custom UI is built.
The text was updated successfully, but these errors were encountered: