studio1337

I figured out where the issue lies. It’s with Advanced Custom Fields. I didn’t think it was theme-related, but I didn’t think ACF would be the cause either.

I’ve been using ACF for ~10 years and I’ve never seen it override this option, on classic or Gutenberg WP (we have lifetime dev license – all the pro features and whatnot – never had this issue). I certainly didn’t add the setting that removes custom fields from post scope. So this was unexpected. I will check with ACF support.

If anyone sees a similar issue, disable ACF. If the custom fields option comes back, contact their support I guess.

It turns out it was a plug-in issue – go figure. I the site uses Ultimate Member, and that’s where I set up the new ‘admin-lite’ user role. I didn’t see that the plug-in checks the “Force hiding admin bar in frontend” option for you by default when you set up roles. I missed it, and ended up on this wild goose chase. One click and it’s now solved.

Thank you for your response. I’m not sure how the instructions correspond with the UI (I see Question/Answer sets – 236 total), but I exported and opened the JSON file, and I see each message as its own entry in the array, and each one is set up just like this:

{
“messages”: [
{
“role”: “user”,
“content”: “What is XXXXX?”
},
{
“role”: “assistant”,
“content”: “XXXXX is a (followed by definition).”
}
]
},

There’s no system role showing in the file, and all messages are in the identical format above, the first three and all following. Did I miss a step in the setup somewhere? I’ve been using older documentation to get things set up apparently.

Hi Arnaud – I think you meant to post a link to the general contact page in your last reply 🙂 I found the “complete a form” button when I visited that page, and I sent a request to your attention. No rush, and thank you for taking the time to review this. I’ll mark this resolved here, since the plug-in is already fixed from that previous update.

Hello Arnaud – yes, they are using the latest version of the plug-in. We update plug-ins daily (sometimes multiple times per day), but would a new version of plug-in fix the titles that were altered when the faulty version was first released? Is there any way to get those titles back without digging through 8 years of articles and fixing them manually?

What a great tool – that’s the first time I’ve used it, and it works as advertised 🙂

It appears the issue is with Schema and Structured Data For WP – https://wordpress.org/plugins/schema-and-structured-data-for-wp/ . I’ll work with their support to figure out the problem.

Thanks for your help!

• This reply was modified 5 years, 8 months ago by studio1337. Reason: Named the wrong plug-in

Hi Jeff,

Here’s what I did. I switched the theme to TwentyTwenty and turned off all plug-ins with the exception of Disable Gutenberg. Then I added the CPT markup and checked settings. DG is turned off for posts and recipes. Posts are showing Gutenberg as expected, but recipes is still showing the classic editor. Is there a custom post type setting that needs to be in place in order for Gutenberg to interact with it properly?

Here’s the code I inserted – let’s try marking it up properly this time 🙂

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: RECIPRE 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,
		)
	);
}

Thanks again for your help!

Sorry – I botched the markdown. My head was in shortcodes, and I used BBCode. I thought I would be able to edit my post, but apparently only the first post can be edited for a limited time.