<?php
/**
 * Plugin Name:       SignSealer
 * Plugin URI:        https://signsealer.com/integrations
 * Description:       Send waivers, rental agreements and acknowledgments from WordPress, and see who has signed. The signing happens on SignSealer; this plugin holds ids and status, never evidence.
 * Version:           1.17.1
 * Requires at least: 6.4
 * Requires PHP:      7.4
 * Author:            Mashdun LLC
 * Author URI:        https://signsealer.com
 * License:           GPL-2.0-or-later
 * License URI:       https://www.gnu.org/licenses/gpl-2.0.html
 * Text Domain:       signsealer
 * Domain Path:       /languages
 *
 * @package SignSealer
 */

/*
 * What this plugin is, and the three things it refuses to do.
 *
 * A WordPress site sends somebody a document to sign and later wants to know
 * whether they signed it. That is the whole job. Everything that makes the
 * signature worth having -- consent recorded before the signature, the text
 * fingerprinted into every event, a hash chain that breaks if edited -- lives
 * on SignSealer and is reached over its API.
 *
 * So this plugin is deliberately thin, and three limits are load-bearing
 * rather than incidental:
 *
 * 1. **It never renders a signature pad.** Signing happens on SignSealer's
 *    own pages. A canvas in WordPress producing something we then accepted
 *    would make every claim on the certificate untrue -- the certificate says
 *    what our engine observed, and it cannot observe a drawing that arrived
 *    as a form field.
 *
 * 2. **It never stores evidence.** Document ids, a status and a link. If
 *    somebody restores a six-month-old backup of this site, nothing about any
 *    signature changes, because nothing about any signature was here.
 *
 * 3. **It never holds a master credential.** The connection is OAuth, scoped
 *    to one business, and revocable by that business from its own portal
 *    without touching WordPress. There is no key that reaches two accounts.
 *
 * The honest caution, written here because it is the part that costs: a
 * plugin in the WordPress directory is a support surface -- every WordPress
 * version, every PHP version, every conflicting plugin, forever. That is the
 * reason to keep this thin rather than clever.
 */

defined( 'ABSPATH' ) || exit;

define( 'SIGNSEALER_VERSION', '1.17.1' );
define( 'SIGNSEALER_FILE', __FILE__ );
define( 'SIGNSEALER_PATH', plugin_dir_path( __FILE__ ) );
/* The plugin's stylesheets and scripts are files of their own, under assets/ (1.16.2). */
define( 'SIGNSEALER_URL', plugin_dir_url( __FILE__ ) );

/**
 * Where the API is.
 *
 * A constant a site owner may override in `wp-config.php`, because a partner
 * on a branded host points somewhere else and editing plugin files is how a
 * site stops receiving updates.
 */
if ( ! defined( 'SIGNSEALER_API_BASE' ) ) {
	define( 'SIGNSEALER_API_BASE', 'https://api.signsealer.com' );
}

/**
 * Where the SignSealer app is, for the links that send an administrator there
 * to make a template or a form. Overridable for the same reason.
 */
if ( ! defined( 'SIGNSEALER_APP_BASE' ) ) {
	define( 'SIGNSEALER_APP_BASE', 'https://app.signsealer.com' );
}

require_once SIGNSEALER_PATH . 'includes/class-signsealer-connection.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-client.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-texting.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-throttle.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-webhook.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-answers.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-admin.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-start.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-shortcode.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-button.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-documents.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-woocommerce.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-checkout.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-details.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-forms.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-bookings.php';
require_once SIGNSEALER_PATH . 'includes/class-signsealer-automator.php';

/**
 * Wire it up.
 *
 * Everything hangs off hooks rather than running at require time, so a site
 * that has the plugin installed and not connected makes no request to
 * anybody. It does register a shortcode and a block -- both have to exist
 * before a page is rendered, and neither reaches the network.
 */
function signsealer_boot() {
	SignSealer_Connection::register();
	SignSealer_Webhook::register();
	SignSealer_Answers::register();
	SignSealer_Shortcode::register();
	SignSealer_Button::register();

	if ( is_admin() ) {
		SignSealer_Admin::register();
	}

	/*
		The integrations. Each one looks for its plugin and hooks nothing
		when it is absent, so a site without WooCommerce carries no
		WooCommerce code path -- and `plugins_loaded` at the default
		priority runs after every plugin's main file, which is when
		`class_exists( 'WooCommerce' )` and `GFAPI` are true if they ever
		will be.
	*/
	SignSealer_WooCommerce::register();
	SignSealer_Checkout::register();
	SignSealer_Details::register();
	SignSealer_Forms::register();
	SignSealer_Bookings::register();
	/* Uncanny Automator's trigger, loaded from Automator's own hook when it is here (1.17.0). */
	SignSealer_Automator::register();
}
add_action( 'plugins_loaded', 'signsealer_boot' );

/*
	Ninja Forms collects its actions in its own `plugins_loaded` callback,
	which runs before `signsealer_boot` does, so SignSealer's action is
	offered to it as this file loads. The filter is only ever applied by
	Ninja Forms, and does nothing on a site without it.
*/
add_filter( 'ninja_forms_register_actions', array( 'SignSealer_Forms', 'nf_register' ) );

/**
 * WooCommerce's order tables, and its block cart and checkout.
 *
 * Every order this plugin touches goes through `wc_get_order` and the
 * order's own meta methods, never `get_post_meta` on an order id, so it
 * works whether orders live in posts or in their own tables. And each thing
 * it does at checkout has its block half beside the classic one: the Store
 * API's order hook and refusal, the "text me" box as an additional checkout
 * field, and the cart block's button. Saying so is what stops WooCommerce
 * showing "incompatible" beside the plugin's name, and offering to switch a
 * shop back to the classic checkout because of it.
 */
function signsealer_woocommerce_features() {
	if ( class_exists( '\\Automattic\\WooCommerce\\Utilities\\FeaturesUtil' ) ) {
		\Automattic\WooCommerce\Utilities\FeaturesUtil::declare_compatibility( 'custom_order_tables', SIGNSEALER_FILE, true );
		\Automattic\WooCommerce\Utilities\FeaturesUtil::declare_compatibility( 'cart_checkout_blocks', SIGNSEALER_FILE, true );
	}
}
add_action( 'before_woocommerce_init', 'signsealer_woocommerce_features' );

/**
 * Register the block.
 *
 * On `init`, not `plugins_loaded`, which is where the rest of this plugin
 * hangs. Block registration on `plugins_loaded` is too early: the block type
 * registry, the translations and `WP_Block_Type_Registry` are not ready, and
 * the symptom is a block that works in some themes and is silently absent in
 * others. WordPress's own documentation says `init` and means it.
 *
 * It is registered from `block.json`, which names `render.php` as the server
 * renderer -- so the editor and the front end agree by construction rather
 * than by two people keeping them in step.
 */
function signsealer_block() {
	register_block_type( SIGNSEALER_PATH . 'block' );
}
add_action( 'init', 'signsealer_block' );

/**
 * On deactivation, stop asking.
 *
 * The connection is left alone: deactivating a plugin is not the same as
 * disconnecting an account, and somebody deactivating to debug a conflict
 * should not have to reconnect afterwards. Disconnecting is its own button,
 * and it only forgets here: the grant is ended in SignSealer, under
 * Developers -> Connected apps (1.14.4: this used to say it revoked it).
 */
function signsealer_deactivate() {
	wp_clear_scheduled_hook( 'signsealer_refresh_token' );
	/* Each agreement started before an Amelia booking has its own look scheduled (1.16.0); with the plugin off, nothing would answer it. */
	wp_unschedule_hook( SignSealer_Bookings::UNBOOKED_HOOK );
	/* A completed document's answers, asked for after its delivery (1.17.0). */
	wp_unschedule_hook( SignSealer_Answers::HOOK );
}
register_deactivation_hook( __FILE__, 'signsealer_deactivate' );