Benji Kostenbader

@sasiddiqui it looks like this happens on the very first install of the plugin. I was wrong to think it was connected to when we fire wp_insert_post().

We are assigning post_name in the initial wp_insert_post() on these plugins, could that be making part of the error?

We also assign the taxonomies from there with wp_set_object_terms().

I can’t think of how either of those very basic functions might hurt the plugin, but I’m not sure? Finally, here’s our taxonomy setup in case it’s the culprit:

    $labels = array(
        'name' => _x( 'States', 'taxonomy general name' ),
        'singular_name' => _x( 'State', 'taxonomy singular name' ),
        'search_items' =>  __( 'Search States' ),
        'all_items' => __( 'All States' ),
        'parent_item' => __( 'Parent State' ),
        'parent_item_colon' => __( 'Parent State:' ),
        'edit_item' => __( 'Edit State' ), 
        'update_item' => __( 'Update State' ),
        'add_new_item' => __( 'Add New State' ),
        'new_item_name' => __( 'New State Name' ),
        'menu_name' => __( 'States' ),
    );    
  
    register_taxonomy('states',array('community', 'design'), array(
        'hierarchical' => true,
        'labels' => $labels,
        'show_ui' => true,
        'show_in_rest' => true,
        'show_admin_column' => true,
        'query_var' => false,
        'rewrite' => array( 'slug' => 'state' ),
    ));

• This reply was modified 3 years, 3 months ago by Benji Kostenbader.

Hi Sami,

Thanks for the quick response!

We’re running it on a cron, so we can definitely filter the auto-created-redirects there.

Will report back right away with results