jasonrwasser

I am having a similar issue but here is what I’ve found. Not sure if this whole whitelisting thing is relevant given it seems to be an authentication issue.

• Zapier authentication is blocked when connected account is using 2FA
• Zapier authentication is blocked by using reCaptcha via Wordfence.
• Zapier tries to authenticate when you are changing or adding zaps using this connection. If you have both options disabled when you are making these changes everything should work just fine.
• Until this issue is resolved, if you want to use 2FA you need to set up your Zapier connection using a wordpress account that doesn’t have it enabled
• Until this issue is resolved you need to temporarily disable recaptcha when making changes or creating new zaps.

edit: also just to add 2FA blocks the connection even if using the app password

• This reply was modified 2 years, 11 months ago by jasonrwasser.

Thanks so much.

It seems that 4.0 has been officially released now. I can verify that the provided snippet works as described by the plugin author. Closing.

Thank you so much for your thorough response, it was very informative.

These are going to be fresh websites, so I have the luxury of not needing to worry about legacy data from redirects, just setting them up for success in the future.

The snippet you provided worked exactly as described. I’ve done a few extra things to make functional expectations clear to users. I’m going to post the code, in case someone else is having the same issue. This was done quickly so forgive any code slop.

You did mention some additional flexibility with the SEO Bar coming in the next major release. Is there somewhere I can follow the progress of this version?

Anyways, for those who find this ticket and are wanting to make this a bit more user friendly here is what I did.

In functions.php

This snippet is the one provided above by the Plugin Author

add_action( 'the_seo_framework_after_front_init', function() {
	remove_action( 'template_redirect', [ the_seo_framework(), '_init_custom_field_redirect' ] );
} );

This snippet will allow you to add a script to just load on the screens for creating posts/pages and the screen for editing posts/pages (custom post types should also be covered). You will need to change the path on the enqueue to wherever you want to keep your js files. As Sybre mentioned above, this snippet works now, but when they extend this to terms it will need to be tweaked

function admin_posts_enqueue_admin_script( $hook ) {

    if ( 'post.php' === $hook || 'post-new.php' === $hook ) {
        wp_enqueue_script( 'admin_tsf_redirect_disable', get_template_directory_uri() . '/assets/src/temp/admin-tsf-redirect-disable.js', array('jquery'), '2.0' );
    }else{
        return;
    }
}
add_action( 'admin_enqueue_scripts', 'admin_posts_enqueue_admin_script' );

Custom JS file referenced from the enqueue

This is using jquery, but that is by no means required, should be easy enough to recreate in vanilla.

( function( $ ) {

    $(document).ready(function(){
        $('#autodescription_redirect')
            .attr('disabled', 'disabled')
            .attr('placeholder', 'This field has been disabled.*')
            .after('<p>* The redirect field here may conflict with the redirect manager installed on this site. While this has been disabled here, you will have full ability to <a target="_blank" href="/wp-admin/tools.php?page=redirection.php">manage redirects here</a>.</p>');
    });

} )( jQuery );