studio1337

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.

@joa-kim Thank you very much for the recommendation. At a glance, it looks like it checks a lot of our boxes, if not all of them. I’ll give this a try!

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.

Hi Arnaud – I wish I could, but it appears support isn’t available for folks using the free version. I’m never opposed to paying for good development and support, but ultimately it’s up to the client to decide if it’s needed, and it’s going to be a hard sell asking them to buy the plug-in to get support on an issue the free version created. Is there another way to reach you, or do they need to purchase the premium version in order to get things fixed?

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?

Great news Sanjeev – thanks for the update. I’ll let our client know, and we’ll keep an eye out for the next update.

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://www.ads-software.com/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 4 years, 3 months ago by studio1337. Reason: Named the wrong plug-in

Hi Priscilla,

Thank you very much for getting back to me.

1. It is network activated – every site uses it.
2. The subsite address is the correct TLD (as seen in this topic when you’re logged in).
3. I just tried this, and it appears to have worked! I don’t suppose there’s a way to hit the reset on all sites across the network at once? Or would we need to log into each one and reset them individually? It’s not a HUGE problem if needed, just somewhat tedious; if it’s possible to run network-wide, that would be a nice bonus.

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!

That makes sense. I will look for a conflict and let you know what I find.

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.

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…:)

Hi Jeff,

Good question – I checked the error log and nothing registered there. I also tried turning on WordPress debugging, tried saving settings and viewing a recipe post, and while the classic editor is showing, nothing was generated in log files.

I’m happy to share temporary login details privately if you’d like to see the error in action, or I can take screen shots to confirm the settings and results.

Thanks for your help!
Paul

Yes! The biggest flaw in Gutenberg isn’t its bugs or its over-encumbered workflow, though these are certainly issues worthy of low marks. The biggest flaw is that it goes against the whole principle that a well made site with strict branding guidelines should NOT allow end users to arbitrarily use any object of their choice in any order they wish on any page they choose. With tools like ACF, you can very narrowly define how end users manage their pages so they have as much or as little flexibility as they SHOULD have, not as much as WordPress wants EVERYONE to have. There’s a reason developers who use WordPress are not using Wix or SquareSpace. Making WordPress more like those platforms, and making it the core WP experience, defeats that position. Maybe all of this can be worked around, but fighting the editor tooth and nail to pare it down and mold it into something usable is not a worthy use of time, especially when after you’ve done all that, it’s still buggy and still painful for people to use.

Wordpress will only remain useful so long as meta boxes are supported and the classic editor is available. Gutenberg is terrible, not (just) because it’s buggy, but because it fundamentally breaks strong, well managed workflows that developers have established and customized uniquely to each of their clients. It should be optional, at best, and it should prove its value the old-fashioned way, by becoming such an important and beloved tool that moving it into core is a no-brainer, kind of how ACF is all of that right now.

For the past few years, the folks who run in my dev circles and I have been saying that WordPress should make Elliot an offer he can’t refuse and absorb ACF pro into WP core. WordPress picked the WRONG plug-in to incorporate. Your review is Truth with a capital T.