<?php
/**
 * Uninstall cleanup for Acez SEO — removes the plugin's own options and
 * transients when the plugin is DELETED (not merely deactivated) from
 * wp-admin.
 *
 * Post/term meta (_acez_seo_*) is deliberately KEPT: titles and descriptions
 * are user-authored content, and deleting it would make an accidental
 * uninstall destructive and unrecoverable. Reinstalling the plugin picks the
 * meta right back up.
 */

if ( ! defined( 'WP_UNINSTALL_PLUGIN' ) )
{
	exit;
}

$acez_seo_options = array(
	'acez_seo_global_settings',
	'acez_seo_settings_post',
	'acez_seo_settings_page',
	'acez_seo_archive_settings',
	'acez_seo_robots_txt',
	'acez_seo_ai_settings',
	'acez_seo_integrations',
	// The Custom Code feature was removed in 0.9.9.33 (WordPress.org review:
	// no arbitrary code insertion). The option is deliberately NOT deleted on
	// upgrade — an orphaned row is harmless, while dropping user data during an
	// automatic update is not — but it still gets cleaned up on uninstall.
	'acez_seo_custom_code',
	'acez_seo_features',
	'acez_seo_license',
	'acez_seo_cache_version',
	'acez_seo_ai_bots',
	'acez_seo_ai_log',
	'acez_seo_ai_usage',
	'acez_seo_onboarding',
	'acez_seo_sitemap',
);

foreach ( $acez_seo_options as $acez_seo_option )
{
	delete_option( $acez_seo_option );
}

// Dismissed conflict notices are admin UI state, not user-authored content.
delete_metadata( 'user', 0, 'acez_seo_dismissed_conflicts', '', true );

// Dynamic option families (per post type / per taxonomy) and our transients.
global $wpdb;

$wpdb->query( "DELETE FROM {$wpdb->options} WHERE option_name LIKE 'acez\\_seo\\_settings\\_%' OR option_name LIKE 'acez\\_seo\\_location\\_rules\\_%' OR option_name LIKE 'acez\\_seo\\_archive\\_settings\\_%'" ); // phpcs:ignore WordPress.DB.DirectDatabaseQuery
$wpdb->query( "DELETE FROM {$wpdb->options} WHERE option_name LIKE '\\_transient\\_acez\\_seo\\_%' OR option_name LIKE '\\_transient\\_timeout\\_acez\\_seo\\_%'" ); // phpcs:ignore WordPress.DB.DirectDatabaseQuery