Hi Jeff – I’ll give this a try, but it may not be as easy as it sounds.
1) Install default WP
2) Install plug-ins. Here’s a full list, but likely only a couple might cross paths with DG functionally.
Advanced Custom Fields PRO
Disable Gutenberg
Divi Builder
Duplicate Post
Elegant Themes Updater
Gravity Forms
Post Type Switcher
Smush
WP-PageNavi
Yoast SEO
Zip Recipes
3) Create CPT for Recipes. Here’s what I have in the functions folder (some of these settings are redundant because they’re default, but I don’t think that shouldn’t impact anything):
[code]add_action( 'init', 'create_custom_taxonomies', 0 );
function create_custom_taxonomies() {
// RECIPES
$labels = array(
'name' => _x( 'Recipe Categories', 'taxonomy general name' ),
'singular_name' => _x( 'Recipe Category', 'taxonomy singular name' ),
'search_items' => __( 'Search Recipe Categories' ),
'all_items' => __( 'All Recipe Categories' ),
'parent_item' => __( 'Parent Recipe Category' ),
'parent_item_colon' => __( 'Parent Recipe Category:' ),
'edit_item' => __( 'Edit Recipe Category' ),
'update_item' => __( 'Update Recipe Category' ),
'add_new_item' => __( 'Add New Recipe Category' ),
'new_item_name' => __( 'New Recipe Category Name' ),
'menu_name' => __( 'Recipe Category' ),
);
$args = array(
'public' => true,
'hierarchical' => true,
'labels' => $labels,
'show_ui' => true,
'show_admin_column' => true,
'query_var' => true,
);
register_taxonomy( 'recipe-categories', array( 'recipes' ), $args );
}
add_action( 'init', 'create_post_type' );
function create_post_type() {
// REGISTER NEW POST TYPE: RECIPE POSTS
register_post_type( 'recipes',
array(
'labels' => array(
'name' => __( 'Recipe Posts' ),
'singular_name' => __( 'Recipe Post' )
),
'public' => true,
'show_ui' => true,
'has_archive' => true,
'exclude_from_search' => false,
)
);
}[/code]
4) Move a handful of posts from the blog (Posts) to recipes (Recipe Posts).
5) Make sure ‘Post Type = recipes’ is unchecked in DG settings (it was unchecked by default after I created the new post type).
6) Check a recipe post to see whether Gutenberg is enabled.
Divi Builder is turned on for this post type (we’re carrying over old posts from a previous build, and needed to have this installed), and it similarly determines whether particular editing functions are available for a post type. Maybe there’s a conflict?
Also, Zip Recipes creates a hidden CPT, but this doesn’t appear to generate a post-type. I looked through the plug-in to see if I could find a post type registered, and I wasn’t able to find a register_post_type (I checked plug-in-root files manually, and ran grep -r register_post_type * to see if the command was present anywhere in the plug-in). So I’m pretty certain that DG setting is for the CPT I created manually. Also, the CPT slug matches the one I entered when I preview the post.
I don’t know if this whole process will bear much; maybe it helps just having the list of plug-ins and CPT code? We know DG is affecting the post type; otherwise, the classic editor would not display. So it’s not ignoring it. It’s definitely affecting it. It’s just a matter of making it *not* affect it…:)
