f086b89e2d
Consolidates the `peptide` CPT under PR Core ownership, dropping the `pr_peptide` slug-collision that was 404ing all 89 peptide detail pages. - POST_TYPE: pr_peptide -> peptide - TAX_CATEGORY: pr_peptide_category -> peptide_category - TAX_FAMILY + pr_peptide_family taxonomy removed - Defensive post_type_exists/taxonomy_exists guards on both registrations - Args harmonized as superset of PSA + prior PR Core (adds thumbnail support) - Activation hook + init:999 version-change flush handler - Uninstall scoped to _pr_core_authored flag (PSA-authored posts survive) - Plugin version 0.1.1 -> 0.2.0, CHANGELOG in same commit - ARCHITECTURE.md + CONVENTIONS.md updated with CPT ownership rule QA gate verdict: PASS (qa-reviews/peptide-repo-core/2026-04-22-874f93b.md) Sibling release: peptiderepo/peptide-search-ai#15 (PSA v4.5.0) Known follow-up: manage_peptide_content capability is not granted to any role as of v0.2.0. No current UI/theme reads or writes PR Core-defined meta keys, so no regression. Follow-up thread to decide role assignment.
89 lines
3.0 KiB
PHP
89 lines
3.0 KiB
PHP
<?php
|
|
/**
|
|
* Peptide Repo Core — Selective data teardown on uninstall.
|
|
*
|
|
* Removes plugin-owned data only: custom tables, PR Core-authored peptide
|
|
* posts, pr_core_ options, and the manage_peptide_content capability.
|
|
* Shared data (the 89 canonical peptide posts authored by PSA, and the
|
|
* peptide_category taxonomy terms) is preserved.
|
|
*
|
|
* @see ARCHITECTURE.md — §2.9 Uninstall specification.
|
|
*/
|
|
|
|
if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) ) {
|
|
exit;
|
|
}
|
|
|
|
global $wpdb;
|
|
|
|
/* ── 1. Drop custom tables ────────────────────────────────────────────── */
|
|
|
|
$tables = [
|
|
$wpdb->prefix . 'pr_dosing_rows',
|
|
$wpdb->prefix . 'pr_legal_cells',
|
|
$wpdb->prefix . 'pr_ai_candidate_queue',
|
|
];
|
|
|
|
foreach ( $tables as $table ) {
|
|
// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery, WordPress.DB.DirectDatabaseQuery.SchemaChange
|
|
$wpdb->query( "DROP TABLE IF EXISTS {$table}" );
|
|
}
|
|
|
|
/* ── 2. Delete only peptide posts authored through PR Core's UI ───────── */
|
|
|
|
/*
|
|
* As of v0.2.0, PR Core shares the `peptide` CPT with Peptide Search AI.
|
|
* PSA authored the 89 canonical peptide posts on peptiderepo.com; those
|
|
* predate PR Core and do NOT carry the `_pr_core_authored` flag. A blanket
|
|
* DELETE here would destroy site-owned content, not plugin-owned content.
|
|
*
|
|
* This loop only deletes posts that PR Core itself created (flagged with
|
|
* post-meta `_pr_core_authored = '1'`). If no post carries the flag, the
|
|
* loop no-ops and shared content is preserved.
|
|
*/
|
|
// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery
|
|
$post_ids = $wpdb->get_col(
|
|
$wpdb->prepare(
|
|
"SELECT p.ID FROM {$wpdb->posts} p
|
|
INNER JOIN {$wpdb->postmeta} pm
|
|
ON p.ID = pm.post_id AND pm.meta_key = %s AND pm.meta_value = %s
|
|
WHERE p.post_type = %s",
|
|
'_pr_core_authored',
|
|
'1',
|
|
'peptide'
|
|
)
|
|
);
|
|
|
|
foreach ( $post_ids as $post_id ) {
|
|
wp_delete_post( (int) $post_id, true );
|
|
}
|
|
|
|
/* ── 3. Preserve taxonomy terms (shared ownership post-v0.2.0) ────────── */
|
|
|
|
/*
|
|
* `peptide_category` is shared between PR Core and PSA. Term metadata
|
|
* (descriptions, parent relationships, counts) is data the site owns —
|
|
* removing it on PR Core uninstall would strip categorization from the
|
|
* peptide posts that remain. So we intentionally do NOT enumerate or
|
|
* delete terms here. `pr_peptide_family` is gone in v0.2.0 so no cleanup
|
|
* is needed for it either.
|
|
*/
|
|
|
|
/* ── 4. Delete all pr_core_ prefixed options ──────────────────────────── */
|
|
|
|
// phpcs:ignore WordPress.DB.DirectDatabaseQuery.DirectQuery
|
|
$wpdb->query(
|
|
"DELETE FROM {$wpdb->options} WHERE option_name LIKE 'pr\_core\_%'"
|
|
);
|
|
|
|
/* ── 5. Remove manage_peptide_content capability from all roles ───────── */
|
|
|
|
$editable_roles = wp_roles()->roles;
|
|
|
|
foreach ( array_keys( $editable_roles ) as $role_name ) {
|
|
$role = get_role( $role_name );
|
|
if ( $role && $role->has_cap( 'manage_peptide_content' ) ) {
|
|
$role->remove_cap( 'manage_peptide_content' );
|
|
}
|
|
}
|