peptide-repo/peptide-repo-core
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(cpt): remove rest_namespace so Gutenberg block editor can load peptide posts (v0.2.2)

Browse Source
This commit is contained in:
peptiderepo
2026-04-24 18:42:20 +00:00
parent c17718b533
commit 0519d6ec7d
1 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
includes/cpt/class-pr-core-peptide-cpt.php
View File

@@ -183,7 +183,10 @@ class PR_Core_Peptide_CPT {
'show_in_nav_menus' => true, 'show_in_nav_menus' => true,
'show_in_rest' => true, 'show_in_rest' => true,
'rest_base' => 'peptides', 'rest_base' => 'peptides',
'rest_namespace' => 'pr-core/v1', // Note: 'rest_namespace' is deliberately omitted. Custom namespaces prevent
// Gutenberg's block editor from loading posts for editing (it fetches the
// hardcoded wp/v2 REST route). WordPress defaults to wp/v2 — appropriate for
// this CPT — and keeps the REST endpoint at /wp-json/wp/v2/peptides/.
'menu_position' => 25, 'menu_position' => 25,
'menu_icon' => 'dashicons-database', 'menu_icon' => 'dashicons-database',
'capability_type' => 'post', 'capability_type' => 'post',
@@ -285,11 +288,4 @@ class PR_Core_Peptide_CPT {
/** /**
* Sanitize editorial_review_status to allowed enum values. * Sanitize editorial_review_status to allowed enum values.
* *
* @param mixed $value Raw input.
* @return string Valid enum value.
*/
public static function sanitize_review_status( $value ): string {
$value = sanitize_text_field( (string) $value );
return in_array( $value, self::REVIEW_STATUSES, true ) ? $value : 'draft';
}
}