Workaround to avoid crashing bbPress' frontend profile page #414
Conversation
class-two-factor-core.php
Outdated
| @@ -925,6 +925,11 @@ public static function manage_users_custom_column( $output, $column_name, $user_ | |||
| * @param WP_User $user WP_User object of the logged-in user. | |||
| */ | |||
| public static function user_two_factor_options( $user ) { | |||
|
|
|||
| /* workaround for two factor options crashing bbpress' profile page */ | |||
| if ( function_exists('bbp_is_user_home_edit') && bbp_is_user_home_edit() ) return; | |||
There was a problem hiding this comment.
This is currently relying on a specific integration and historically this plugin doesn't have any conditional logic to account for specific integrations. Could we somehow convert this into something that can be placed in the class-two-factor-compat.php file which currently deals with Jetpack specific things?
https://github.com/WordPress/two-factor/blob/master/class-two-factor-compat.php
Which of the functionality in this method is actually not compatible with the front-end output?
There was a problem hiding this comment.
You might want to check out my comment where I outline frontend integration with this problem (and a few more) here: #335 (comment)
For this specific issue, it would probably be better to redeclare the admin functions on the frontend when needed.
There was a problem hiding this comment.
This is currently relying on a specific integration and historically this plugin doesn't have any conditional logic to account for specific integrations. Could we somehow convert this into something that can be placed in the
class-two-factor-compat.phpfile which currently deals with Jetpack specific things?https://github.com/WordPress/two-factor/blob/master/class-two-factor-compat.php
Which of the functionality in this method is actually not compatible with the front-end output?
I updated the PR to include an example error screenshot.
Until the required admin functions are exposed on the frontend (should they?), it might be possible to rewrite the workaround in the compat file to conditionally remove the two action hooks instead. I'll look into this.
…o-factor-compat class; Also changed function check from bbp_is_user_home_edit() to bbp_is_single_user_edit() as this is more generally used
CryoutCreations
force-pushed
the
master
branch
from
2770524 to
98f8893
Compare
|
Per @kasparsd's request I moved the bbPress conditionality check to the Hopefully the code now meets the logic separation requirements. |
|
Per yesterday's bug scrub, while we want to be compatible with official plugins we're going to punt this to a future release so that the 0.8.0 release can focus on the U2F deprecation. |
This workarounds skips the addition of the TwoFactor fields to the user profile when it's part of bbPress' frontend profile edit page. These are settings that shouldn't probably by editable on the forum profile anyway.
Fixes the
Fatal error: Uncaught Error: Call to undefined function convert_to_screen()reported in #175Frontend profile page error example:
