← All changes | includes/core/rest-api/class-server.php +13 -0 3.13.1 → 3.13.3 View file →

		@@ -86,11 +86,15 @@
86	86	{
87	87	return apply_filters( 'wpfunnels/rest_api_controllers', array(
88	88	'mcp_settings' => 'McpSettingsController',
89	89	'settings' => 'SettingsController',
	90	+ // The React settings screen (?page=wpfunnels#/settings).
	91	+ 'settings_page' => 'SettingsPageController',
90	92	'templates_library' => 'TemplateLibraryController',
91	93	'order_bump' => 'OrderBumpController',
92	94	'funnel_control' => 'FunnelController',
	95	+ // Funnel listing screen (?page=wpfunnels#/funnels).
	96	+ 'funnel_list' => 'FunnelListController',
93	97	'offer' => 'OfferController',
94	98	'step_control' => 'StepController',
95	99	'remote_funnel' => 'RemoteFunnelsController',
96	100	'products' => 'ProductsController',
		@@ -100,9 +104,18 @@
100	104	'report' => 'DashboardController',
101	105	'plugin_installer' => 'PluginInstallerController',
102	106	'setup_wizard' => 'SetupWizardController',
103	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	+ */
104	116	'automation' => 'WpfnlAutomationController',
	117	+ 'automation_canvas_crud' => 'WpfnlAutomationController',
105	118	'ai_chat' => 'AiChatController',
106	119	'ai_generate' => 'SingleShotAiController',
107	120	));
108	121	}