Francis Chandler

So I dissociated the taxonomies from their post types and saved them. I then renamed them, migrated the terms, cleared and then repopulated the the labels with the new name, made sure the old name was not represented in any of the fields, and then saved the new version. They are now working with Gutenberg and the back end correctly.

I made a user profile on my test site. You should have gotten and email.

I do have a live testing site that we could play on. I added CPTUI and imported the two types and again have the issue in Gutenberg. I am kind of new to some of this, so how would I give you access?

I was wondering it that naming practice could be exacerbating my problems.

I also understand the control or influence aspect.

The “Post Type Slug”s are image and photo

For image
REST API base slug: images
Custom Rewrite Slug: left blank
Custom Query Var Slug: left blank

For photo
REST API base slug: photos
Custom Rewrite Slug: left blank
Custom Query Var Slug: left blank

I have done this same process for five sites. The other four have not had issues with Gutenberg.

Thanks for responding. As to your understanding;

1. yes
2. yes, after creating the content type I exported it with WP Import Export Lite as a csv. I created a query in Drupal Views to fit the desired output into a csv file, imported it with WP Import Export Lite.
3. Using Gutenberg block editor threw the error and prevented editing or adding posts with a tag. Using Classic Editor allows for editing, and tagging. However, in the Admin section for the Photo CPT taxonomy it displays the correct number of entries per tag, but when I click on the number to go to those posts, nothing is shown. I can click the All, and it will show all. Whereas, with the Image CPT taxonomy it shows the posts sorted, and when I click on that number it shows only those posts with that tag.
4. Concerning: “Nothing regarding the settings got imported into the install from Drupal, correct?” That is correct, only data was imported. When I exported the CPTs, I added all fields, which was probably not necessary (possible WordPress nubie mistake). That added custom fields that show in Classic Editor, but are not visible in Gutenberg.

I do now have the site on a live server, and could give access if needed.

I am having a similar issue (and more). AIOSEO can’t read or write to robots.txt. It says there is a robots.txt and it needs to be deleted, but can’t do it. Although I pasted the preview code in it, and it appears to be being read by google (although google is having issues with other parts). The AIOSEO site analysis reports “Your robots.txt file is missing or unavailable”, when there is one there. False negative?

It says to edit my page and links to the one I use as my static front, but have no idea on the page where to change it. Under the advanced tab. I see where I can click, and not use defaults, but none of those options look like anything I want.