← All changes | app/Hooks/actions.php +8 -6 2.2.0 → 2.5.0 View file →

		@@ -2,14 +2,10 @@
2	2
3	3	defined('ABSPATH') || exit;
4	4
5	5	/**
6		- * All registered action's handlers should be in app\Hooks\Handlers,
7		- * addAction is similar to add_action and addCustomAction is just a
8		- * wrapper over add_action which will add a prefix to the hook name
9		- * using the plugin slug to make it unique in all wordpress plugins,
10		- * ex: $app->addCustomAction('foo', ['FooHandler', 'handleFoo']) is
11		- * equivalent to add_action('slug-foo', ['FooHandler', 'handleFoo']).
	6	+ * Handlers live in app/Hooks/Handlers. addCustomAction('foo', ...) is
	7	+ * add_action('slug-foo', ...), prefixed with the plugin slug.
12	8	*/
13	9
14	10	/**
15	11	* @var $app FluentBooking\Framework\Foundation\Application
		@@ -26,8 +22,14 @@
26	22	(new \FluentBooking\App\Hooks\Handlers\AdminMenuHandler())->register();
27	23	(new \FluentBooking\App\Hooks\Scheduler\FiveMinuteScheduler())->register();
28	24	(new \FluentBooking\App\Hooks\Scheduler\DailyScheduler())->register();
29	25	(new \FluentBooking\App\Services\LandingPage\LandingPageHandler())->boot();
	26	+
	27	+/*
	28	+ * MCP server for AI agents. Off by default: until enabled in Settings, boot()
	29	+ * only registers the Toolkit discovery filters. See docs/mcp-server-spec.md.
	30	+ */
	31	+\FluentBooking\App\Modules\MCP\MCPInit::boot();
30	32
31	33
32	34	/*
33	35	* Register all the single action handlers