Closed bobbingwide closed 1 year ago
But when it came to defining wp_template_part I got a Fatal error from Yoast SEO on the Template Parts admin page.
I deactivated and reactivated Yoast SEO and was not able to recreate the problem immediately.
I've reproduced the Fatal error. It occurs when you delete a post.
This issue was intially raised as Extract logic that enables text editing of wp_template, wp_template_part and wp_navigation to a separate plugin.
It's been hijacked by the WordPress SEO problem. Subsequently I've created a new plugin to satisfy the original requirement. See gbcptedit plugin.
I retested the Fatal error problem today in blocks.wp.a2z with WordPress SEO 20.2.1, WordPress 6.1.1 and Gutenberg 15.3.1
The gbcpedit is now available but I still need to check if I've removed the extra logic from the theme.
Fixed in https://github.com/bobbingwide/fizzie/commit/4700c893a586155f3e2c3eeae82c7b0d54285940 delivered in v1.2.0
While updating Fizzie to work with later versions of Gutenberg ( 12.1.0 and above ) and/or WordPress 5.9 I felt I still needed the ability to (re-)enable editing of
wp_template
andwp_template_part
. See #72 - starting from https://github.com/bobbingwide/fizzie/issues/72#issuecomment-1005604978s.b/wp55/fizzie
.wp_navigation
posts in the text editor so I updated this post type's definition as well.editor
support for thewp_navigation
post type.Now I want to reproduce this capability in blocks.wp.a2z. So I used oik-types again. But when it came to defining
wp_template_part
I got a Fatal error from Yoast SEO on the Template Parts admin page.Requirement
To be able to easily copy the HTML for updated themes back into the theme's source repository while testing with both the latest version of Gutenberg and WordPress in multiple development environments.
Proposed solution