← All changes | includes/core/rest-api/class-server.php +17 -1 3.12.2 → 3.13.3 View file →

		@@ -84,12 +84,17 @@
84	84	*/
85	85	protected function get_controllers()
86	86	{
87	87	return apply_filters( 'wpfunnels/rest_api_controllers', array(
	88	+ 'mcp_settings' => 'McpSettingsController',
88	89	'settings' => 'SettingsController',
	90	+ // The React settings screen (?page=wpfunnels#/settings).
	91	+ 'settings_page' => 'SettingsPageController',
89	92	'templates_library' => 'TemplateLibraryController',
90	93	'order_bump' => 'OrderBumpController',
91	94	'funnel_control' => 'FunnelController',
	95	+ // Funnel listing screen (?page=wpfunnels#/funnels).
	96	+ 'funnel_list' => 'FunnelListController',
92	97	'offer' => 'OfferController',
93	98	'step_control' => 'StepController',
94	99	'remote_funnel' => 'RemoteFunnelsController',
95	100	'products' => 'ProductsController',
		@@ -99,10 +104,21 @@
99	104	'report' => 'DashboardController',
100	105	'plugin_installer' => 'PluginInstallerController',
101	106	'setup_wizard' => 'SetupWizardController',
102	107	'store_checkout' => 'StoreCheckoutController',
	108	+ /*
	109	+ * Two different controllers answer to automations, and WPFunnels Pro
	110	+ * overwrites the 'automation' key with its own CRM controller (see
	111	+ * wpfunnels_add_analytics_controller in wpfnl-pro.php). Keeping this
	112	+ * one under its own key means both register instead of the Pro one
	113	+ * silently replacing it — which is what left the wpfnl/v1 namespace
	114	+ * with no routes at all whenever Pro was active.
	115	+ */
103	116	'automation' => 'WpfnlAutomationController',
104		- ));
	117	+ 'automation_canvas_crud' => 'WpfnlAutomationController',
	118	+ 'ai_chat' => 'AiChatController',
	119	+ 'ai_generate' => 'SingleShotAiController',
	120	+ ));
105	121	}
106	122
107	123	/**
108	124	* Return the path to the package.