<?php
/**
 * Plugin bootstrap.
 *
 * @package Debug_Log_Router
 */

defined( 'ABSPATH' ) || exit;

/**
 * Hooks the plugin into a normal WordPress request.
 */
class DLOGR_Plugin {

	/**
	 * Registers the plugin's hooks.
	 *
	 * @return void
	 */
	public static function init() {
		/*
		 * No load_plugin_textdomain() (2026-10-11): translations come as
		 * language packs from translate.wordpress.org, and core loads those
		 * by itself, just in time, from wp-content/languages/plugins. The
		 * plugin ships no .po or .mo files of its own.
		 */
		if ( is_admin() ) {
			DLOGR_Admin::init();

			/*
			 * Registered beside the page rather than inside it: the download
			 * answers on admin-post.php, which is admin enough for is_admin()
			 * and is not our page at all.
			 */
			DLOGR_Download::init();

			/*
			 * The interface language setting, admin only. Every string of this
			 * domain lives in DLOGR_Admin and DLOGR_Download, and the options are
			 * not autoloaded, so hooking this everywhere would cost every visitor
			 * a query for nothing. Разбор - development/docs/perevod.md.
			 */
			add_filter( 'override_load_textdomain', array( __CLASS__, 'override_textdomain' ), 10, 2 );
		}

		/*
		 * The loader reports damage through constants: no data file, which is
		 * what a block pasted in by hand leaves behind, and no marked log
		 * directory, which is what deleting it over FTP leaves behind. Both
		 * stop logging silently, and the loader is the only thing that sees
		 * either one on an ordinary request. Repairing on wp_loaded means any
		 * request does it: front, admin, cron, REST, CLI. Not earlier: a plugin
		 * may change the REST prefix on init.
		 */
		add_action( 'wp_loaded', array( 'DLOGR_Boot', 'maybe_repair' ) );

		// Drift between the file and the database is only worth a query in the admin.
		add_action( 'admin_init', array( 'DLOGR_Boot', 'repair_boot_data' ) );

		/*
		 * Activation hooks do not run on a plugin update, so the journal table
		 * would never learn about a schema change. Same reason boot-data.json is
		 * repaired on wp_loaded, and the admin is enough: nothing writes to the
		 * journal that the front end alone could trigger before an admin ever
		 * loads a page.
		 */
		add_action( 'admin_init', array( 'DLOGR_Journal', 'maybe_install' ) );
	}

	/**
	 * Languages the plugin's texts can be switched to, besides the profile one.
	 *
	 * English only (заказчик, 2026-10-11). The switch exists for English:
	 * PHP messages are English, people search for them in English, and
	 * screenshots go to support. Any other language is the profile's, which
	 * core loads from its language pack by itself. Until then Russian and
	 * German could be picked across profiles too, from files the plugin
	 * shipped - and those files are gone, see init().
	 *
	 * Native names, never translated: this list is for somebody who cannot read
	 * the interface as it stands, the way WordPress names languages in its own
	 * selector. The setting's sanitising and the drop-down both read it here, so
	 * the two cannot drift apart.
	 *
	 * @return array Locale code => native name.
	 */
	public static function languages() {
		return array(
			'en_US' => 'English',
		);
	}

	/**
	 * Keeps this plugin's texts in English when that is the chosen language.
	 *
	 * Answering "already loaded" makes core open no file at all, and __() hands
	 * back the source text. Other domains get their value back untouched: this
	 * filter runs for every text domain on the page.
	 *
	 * @param bool   $override Whether loading is already taken over.
	 * @param string $domain   Text domain being loaded.
	 * @return bool
	 */
	public static function override_textdomain( $override, $domain ) {
		if ( 'debug-log-router' !== $domain ) {
			return $override;
		}

		return 'en_US' === DLOGR_Settings::get( 'interface_language' ) ? true : $override;
	}
}