Memory Wiki

I'll start by reading the existing mu-plugin and then systematically search every layer of the codebase.

Now let me run all the systematic searches in parallel:

Now let me read the critical backend files that contain the key gate mechanisms:

Let me read the file from inside the Docker container:

Let me use docker exec to read the key sections of AdminMenu.php. I'll extract the getAdminVars() method and the FLUENTCAMPAIGN check:

Let me read more critical areas:

Let me check the critical remaining files:

Let me check a few more critical areas:

Let me also check how `has_campaign_pro` is defined globally across components, and check the remaining files:

Let me check one more vital piece - how the ProFunnelItems blocks are marked with `is_pro`:

Now I have comprehensive data. Let me compile the complete exhaustive report. --- ## EXHAUSTIVE REPORT: FluentCRM Paywall/Upgrade/Pro Gates ### SUMMARY OF THE GATING ARCHITECTURE The gating system centers on a single PHP constant: **`FLUENTCAMPAIGN`** (and related: `FLUENTCAMPAIGN_FRAMEWORK_VERSION`, `FLUENTCAMPAIGN_DIR_FILE`). The mu-plugin defines `FLUENTCAMPAIGN=true`, `FLUENTCAMPAIGN_FRAMEWORK_VERSION=3`, and later `FLUENTCAMPAIGN_DIR_FILE` (at `init` priority 5). This unlocks ~95% of gates. Remaining unhandled issues are subtle. --- ## GATE CATEGORY 1: PHP BACKEND GATES (FLUENTCAMPAIGN constant) ### Gate 1.1: `FunnelHandler` — ProFunnelItems loading **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Hooks/Handlers/FunnelHandler.php` **Line:** 100 **Mechanism:** `if (!defined('FLUENTCAMPAIGN_DIR_FILE')) { new \FluentCrm\App\Services\Funnel\ProFunnelItems(); }` **What it gates:** All Pro funnel triggers (WooCommerce, PMPro, MemberPress, LearnDash, etc.) and Pro funnel blocks (conditional actions, sequence emails, webhooks, etc.) **Already handled:** ✅ YES — mu-plugin defines `FLUENTCAMPAIGN_DIR_FILE` at `init` priority 5, which is AFTER the `registerFunnelItems()` call (which runs at `init` priority 1). The check `!defined('FLUENTCAMPAIGN_DIR_FILE')` evaluates to `true` at priority 1, so ProFunnelItems IS loaded. This is the correct deferred approach. ### Gate 1.2: ProFunnelItems — All Pro triggers marked `disabled=true` **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Funnel/ProFunnelItems.php` **Lines:** ~140-650+ **Mechanism:** Every Pro trigger has `'disabled' => true`. The triggers include: WooCommerce (new order, completed, refunded, subscription), PMPro (enrolled, expired), MemberPress, LearnDash, LifterLMS, EDD, Restrict Content Pro, TutorLMS, Wishlist Member, SureCart, Abandoned Cart, AffiliateWP, etc. **Already handled:** ✅ PARTIALLY — The mu-plugin has a filter at line 70-82 that only handles PMPro triggers (`pmpro_after_change_membership_level`, `pmpro_membership_post_membership_expiry`). **All other Pro triggers remain `disabled=true`**. This is a significant gap. ### Gate 1.3: ProFunnelItems — All Pro blocks marked `is_pro=true` **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Funnel/ProFunnelItems.php` **Lines:** ~340-500+ **Mechanism:** Every Pro block has `'is_pro' => true`. Blocks include: Has In Selected Lists, Has Selected Tags, Link Click benchmark, Send Campaign Email, Cancel Automations, Cancel Sequence Emails, Set Sequence Emails, Update Contact Property, Add Notes & Activity, Outgoing Webhook, End This Funnel Here, Check Contact's Properties, Create WordPress User, Update WP User Meta, Change WP User Role, EDD benchmarks, WooCommerce purchased checks, etc. **Already handled:** ✅ YES — The blocks' `is_pro` flag is read by the JS frontend (BlockChoice component), but the rendering in the funnel editor checks `window.fcAdmin.addons.fluentcampaign` which is true. However, the `disabled` triggers' `upgrade` buttons link to `crm_pro_url`. ### Gate 1.4: FunnelController — Automation sync (cleanup) **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Http/Controllers/FunnelController.php` **Line:** 1342 **Mechanism:** `if (!defined('FLUENTCAMPAIGN_DIR_FILE')) { return sendError('requires latest version of FluentCRM Pro'); }` **What it gates:** The `syncAutomationSteps` cleanup feature **Already handled:** ✅ YES — `FLUENTCAMPAIGN_DIR_FILE` is defined by mu-plugin. ### Gate 1.5: SubscriberController — `add_to_email_sequence` bulk action **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Http/Controllers/SubscriberController.php` **Line:** 1237 **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { return $this->sendError(['message' => 'requires FluentCRM Pro']); }` **What it gates:** Adding contacts to email sequences via bulk action **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined by mu-plugin. ### Gate 1.6: SubscriberController — `add_to_automation` bulk action **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Http/Controllers/SubscriberController.php` **Line:** 1400 **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { return $this->sendError(['message' => 'requires FluentCRM Pro']); }` **What it gates:** Adding contacts to automation funnels via bulk action **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined. ### Gate 1.7: SettingsController — Tag-based double optin redirect **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Http/Controllers/SettingsController.php` **Line:** 194 **Mechanism:** `'disabled' => !defined('FLUENTCAMPAIGN')` — the setting field is disabled without Pro **What it gates:** Tag-based double optin redirect feature **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined, so `disabled` is `false`. ### Gate 1.8: Helper.php — Email sequence options in cascade selection **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Helper.php` **Line:** 605 (in `getCascadeSelectionOptions`) **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { return ['options' => []]; }` — returns empty options for email_sequences **What it gates:** Email sequence selection dropdowns in the UI **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined. ### Gate 1.9: Helper.php — WooCommerce purchase history segment fields (Pro-only) **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Helper.php` **Line:** ~1701 **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { ... add Pro-only fields like 'total_order_count' with label '(Pro Required)' ... }` **What it gates:** WooCommerce-based segment filtering fields **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined, so the Pro-only fields are available normally. ### Gate 1.10: Helper.php — PMPro purchase history provider **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Helper.php` **Line:** 790 **Mechanism:** `if (defined('PMPRO_VERSION') && defined('FLUENTCAMPAIGN'))` — PMPro purchase history requires both PMPro active AND FluentCRM Pro **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined. ### Gate 1.11: Helper.php — Visual Builder template (paywall version) **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Helper.php` **Line:** 605-612 (in `getEmailDesignTemplates`) **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { $templates['visual_builder'] = [template_type => 'visual_builder_demo']; }` — without Pro, adds a "Visual Builder" option that is only a demo (not functional) **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined, so the demo template entry is NOT added. When `FLUENTCAMPAIGN` IS defined, the template comes from the Pro plugin itself. ### Gate 1.12: OptionsController — Email sequence options **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Http/Controllers/OptionsController.php` **Line:** 543 **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { return ['options' => []]; }` — returns empty options **What it gates:** Email sequence options for AJAX requests **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined. ### Gate 1.13: Helper.php — `getPurchaseHistoryProviders` PMPro check **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Services/Helper.php` **Line:** 790 **Mechanism:** `if (defined('PMPRO_VERSION') && defined('FLUENTCAMPAIGN'))` — PMPro purchase history requires both **Already handled:** ✅ YES. ### Gate 1.14: CampaignUrlMetric — Smart Links filter gate **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Models/CampaignUrlMetric.php` **Line:** 306 **Mechanism:** `if (!apply_filters('fluent_crm/has_smartlink', false))` — the filter `fluent_crm/has_smartlink` returns false by default. The Pro plugin hooks this filter to return true. **Already handled:** ❌ NO — The mu-plugin does NOT hook `fluent_crm/has_smartlink`. Smart Links will not be transformed/rendered. Need to add: `add_filter('fluent_crm/has_smartlink', '__return_true');` ### Gate 1.15: AdminMenu — `hasSmartLink()` method **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Hooks/Handlers/AdminMenu.php` **Lines:** 961-972 **Mechanism:** `if (!defined('FLUENTCAMPAIGN')) { return false; }` then checks for the `fc_smart_links` DB table existence **What it gates:** The `has_smart_link` property in `fcAdmin` admin vars **Already handled:** ✅ PARTIALLY — `FLUENTCAMPAIGN` is defined so it proceeds. But it also needs the `fc_smart_links` DB table to exist. Smart links would only work if the Pro plugin's DB tables were created. ### Gate 1.16: CLI Commands — Multiple FLUENTCAMPAIGN checks **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Hooks/CLI/Commands.php` **Lines:** 112, 332, 552, 702 **Mechanism:** Multiple `if (!defined('FLUENTCAMPAIGN')) { \WP_CLI::error('FluentCRM Pro is required'); }` checks for various CLI commands including sending emails, campaigns, sequences **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined. ### Gate 1.17: PurchaseHistory — PMPro check **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Hooks/Handlers/PurchaseHistory.php` **Line:** 682 **Mechanism:** `if (!defined('FLUENTCAMPAIGN'))` gates PMPro purchase history handler **Already handled:** ✅ YES. ### Gate 1.18: AbandonCart — FluentCart automation trigger gate **Files:** `FluentCartAutomationTrigger.php:62`, `AbandonCartRunner.php:241` **Mechanism:** `if (!defined('FLUENTCAMPAIGN_DIR_FILE'))` — gates abandon cart automation triggers **Already handled:** ✅ YES — `FLUENTCAMPAIGN_DIR_FILE` is defined. ### Gate 1.19: Actions.php — Update notice for outdated Pro **File:** `/var/www/html/wp-content/plugins/fluent-crm/app/Hooks/actions.php` **Lines:** 186-192 **Mechanism:** Admin notice when `FLUENTCAMPAIGN_FRAMEWORK_VERSION < 3` (version check) **Already handled:** ✅ YES — mu-plugin defines version 3. --- ## GATE CATEGORY 2: PHP BACKEND FILTER GATES ### Gate 2.1: `fluentcrm_is_require_verify` filter **File:** `AdminMenu.php:746` and mu-plugin line 37 **Mechanism:** `apply_filters('fluentcrm_is_require_verify', false)` — controls whether verification is required **Already handled:** ✅ YES — mu-plugin has `add_filter('fluentcrm_is_require_verify', '__return_false')`. ### Gate 2.2: `fluentcrm_disable_email_open_tracking` filter **File:** `Helper.php:657` **Mechanism:** `!apply_filters('fluentcrm_disable_email_open_tracking', false)` **Already handled:** ✅ YES — mu-plugin line 38 has `add_filter('fluentcrm_disable_email_open_tracking', '__return_false')`. ### Gate 2.3: `fluent_crm/has_smartlink` filter — Smart Links **File:** `CampaignUrlMetric.php:306` **Mechanism:** Returns false by default; Pro plugin hooks it **Already handled:** ❌ NO — needs `add_filter('fluent_crm/has_smartlink', '__return_true')`. ### Gate 2.4: `fluent_crm/admin_vars` filter — Extensibility **File:** `AdminMenu.php` (end of getAdminVars) **Mechanism:** Filter used by Pro plugin to add more admin vars **Already handled:** ✅ N/A — this is additive, not a gate. --- ## GATE CATEGORY 3: JS/VUE FRONTEND GATES ### Gate 3.1: `window.fcAdmin.addons.fluentcampaign` — Primary JS gating mechanism **Source:** AdminMenu.php `getAdminVars()` → `'addons' => getActivatedFeatures()` **Helper.php `getActivatedFeatures()`:** `'fluentcampaign' => defined('FLUENTCAMPAIGN_FRAMEWORK_VERSION')` **Since:** mu-plugin defines `FLUENTCAMPAIGN_FRAMEWORK_VERSION=3`, this is `true`. **JS access pattern (used in every component):** ```js has_campaign_pro() { var e,t; return !!(null==(t=null==(e=window.fcAdmin)?void 0:e.addons)?void 0:t.fluentcampaign) } ``` **Already handled:** ✅ YES — constant is defined. ### Gate 3.2: Export Contacts (Exporter.js) **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/Exporter.js` **Mechanism:** Render function checks `c.has_campaign_pro` — if false, shows GenericPromo card instead of export form **Already handled:** ✅ YES — `has_campaign_pro` is true. ### Gate 3.3: Campaign Emails (resend, resend unopened, export) **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/_LinkMetrics.js` **Mechanism:** `this.has_campaign_pro` checks in `resendEmail()`, `resendUnopenedEmails()`, `exportCampaignEmails()` — if false, shows error notification **Already handled:** ✅ YES. ### Gate 3.4: Built-in Template Import (BuiltinTemplateDrawer.js) **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/BuiltinTemplateDrawer.js` **Mechanism:** `e.has_campaign_pro` check — if false, the import button shows Pro modal instead of actually importing **Already handled:** ✅ YES. ### Gate 3.5: Scripts RecipientTagger — Advanced Filters **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/ReadableRecipientTagger.js` **Mechanism:** `e.has_campaign_pro` in render — advanced filters section is hidden without Pro **Already handled:** ✅ YES. ### Gate 3.6: Create Funnel Modal — Trigger selection with disabled Pro triggers **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Funnels/Funnels.js` (CreateFunnelModal) **Mechanism:** `has_campaign_pro` computed property, triggers with `disabled: true` show ProBadge and "Upgrade To Pro" link **Already handled:** ✅ PARTIALLY — The triggers are loaded (ProFunnelItems loads them), but they are still marked `disabled`. The mu-plugin only un-disables PMPro triggers (via the `fluentcrm_funnel_triggers` filter). **All other Pro triggers remain disabled** with "Upgrade To Pro" buttons. ### Gate 3.7: Funnel Editor — Conditional Action gate **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Funnels/FunnelEditor/Edit.js` **Mechanism:** `handleConditionAdd()` checks `this.has_campaign_pro` — if false, shows alert "Require FluentCRM Pro" **Already handled:** ✅ YES — `has_campaign_pro` is true. ### Gate 3.8: Funnel Editor — Block insertion with `is_pro` check **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Funnels/FunnelEditor/Edit.js` (BlockChoice component) **Mechanism:** `insert(e, t)` checks `if(t && t.is_pro)` — shows alert "Require FluentCRM Pro" with link to purchase **Already handled:** ✅ YES — the `is_pro` flag exists on block definitions, but the blocks ARE loaded (because ProFunnelItems runs). The blocks would only be blocked if `is_pro` is checked AND Pro isn't active. ### Gate 3.9: Import Funnel (ImportFunnel.js) **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Funnels/ImportFunnel.js` **Mechanism:** Render function checks `a.has_campaign_pro` — if false, shows PromoCard instead of import UI **Already handled:** ✅ YES. ### Gate 3.10: Settings → Advanced Features — Campaign Archive Shortcode **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/v3app/src/Modules/Settings/_AdvancedFeatures.js` **Mechanism:** `o.has_campaign_pro` check — campaign archive shortcode is only shown when Pro is active **Already handled:** ✅ YES. ### Gate 3.11: Settings → AddOns — Multiple Pro-feature gates **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Settings/AddOns.js` **Mechanisms:** - `has_campaign_pro` check for Frontend Portal feature — "Upgrade to Pro" button shown if false - `has_campaign_pro` check for fetching SMS module settings - `has_campaign_pro` check for Campaign Archive shortcode display - `has_campaign_pro` check for "Recommended Plugins → FluentCRM Pro" section **Already handled:** ✅ YES. ### Gate 3.12: Profile Emails — Send Email button **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Profile/Parts/ProfileEmails.js` **Mechanism:** `e.has_campaign_pro && ...` — Send Email button only rendered when Pro is active **Already handled:** ✅ YES. ### Gate 3.13: Profile Emails — Resend Email **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Profile/Parts/ProfileEmails.js` **Mechanism:** `if(!this.has_campaign_pro) return this.$notify.error(...)` — prevents resending without Pro **Already handled:** ✅ YES. ### Gate 3.14: Profile Emails — Email Sequences and Automations sections **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Profile/Parts/ProfileEmails.js` **Mechanism:** Render check `e.has_campaign_pro ? (show sequences + automations) : (hide)` — entire Email Sequences and Automations sub-sections hidden without Pro **Already handled:** ✅ YES. ### Gate 3.15: Profile Notes — Export Notes **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Profile/Parts/ProfileNotes.js` **Mechanism:** `if(!this.has_campaign_pro) return this.$notify.error(this.$t("Notes export feature is only available on pro version"))` **Already handled:** ✅ YES. ### Gate 3.16: Edit Template — Export Template **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/Modules/Email/Templates/EditTemplate.js` **Mechanism:** `if(!this.has_campaign_pro) return this.$notify.error(this.$t("Template_Export_Alert"))` **Already handled:** ✅ YES. ### Gate 3.17: Profile SMS — has_campaign_pro data property **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/v3app/src/Modules/Profile/Parts/ProfileSMS.js` **Mechanism:** `data() { return { has_campaign_pro: false } }` — hardcoded false in the data, but this is overridden by the component's `has_campaign_pro` computed **Already handled:** ✅ The computed `has_campaign_pro` (from global) overrides it. ### Gate 3.18: GenericPromo.js and GenericPromo2.js — The promo card components **Files:** `/var/www/html/wp-content/plugins/fluent-crm/assets/GenericPromo.js`, `GenericPromo2.js`, `PromoCard.js` **Mechanism:** These are the fallback UI components shown when `has_campaign_pro` is false. They display "This is a pro feature" text and a "Upgrade to Pro" button linking to `appVars.crm_pro_url`. **Already handled:** ✅ These are the consequence of gates, not gates themselves. If `has_campaign_pro` is true, they are never rendered. ### Gate 3.19: ProBadge.js **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/ProBadge.js` **Mechanism:** Simple UI badge showing "Pro" text with a crown icon. Used on disabled funnel triggers. **Already handled:** ✅ Visual indicator only. --- ## GATE CATEGORY 4: EMAIL TEMPLATE FOOTER BRANDING ### Gate 4.1-4.5: Email templates show "Powered By FluentCRM" footer **Files:** - `app/Views/emails/web_preview/Template.php:13` - `app/Views/emails/simple/Template.php:91` - `app/Views/emails/block_editor/Template.php:114` - `app/Views/emails/plain/Template.php:94` - `app/Views/emails/raw_classic/Template.php:36` - `app/Views/emails/classic/Template.php:92` **Mechanism:** `<?php if(!defined('FLUENTCAMPAIGN')): ?><p>Powered By <a href="...">FluentCRM</a></p><?php endif; ?>` **What it gates:** Without Pro, email footers include a "Powered By FluentCRM" link. **Already handled:** ✅ YES — `FLUENTCAMPAIGN` is defined, so branding is hidden. --- ## GATE CATEGORY 5: CSS GATES ### Gate 5.1: Pro modal body styling **File:** `/var/www/html/wp-content/plugins/fluent-crm/assets/admin/css/style.css` **Lines:** 9, 15, 19 (scoped to `.promo_block--centered[data-v-...]`) **Mechanism:** CSS for the promo/upgrade card UI component **Already handled:** ✅ This is just styling, not a functional gate. --- ## GATE CATEGORY 6: THE `is_pro` BLOCK FLAG IN FUNNEL BLOCKS ### Gate 6.1: All 19 Pro funnel blocks (in ProFunnelItems.php getProBlocks) **Tags:** Every Pro block has `'is_pro' => true`. When the JS BlockChoice component renders these, it checks `t.is_pro` and shows a ProBadge. **Already handled:** ✅ The blocks ARE loaded because ProFunnelItems is instantiated. The `is_pro` flag triggers an alert in the `insert()` method, but since Pro IS active, the insert proceeds. --- ## GATE CATEGORY 7: CRM PRO URL/BUTTONS ### Gate 7.1: `crm_pro_url` in admin vars **File:** `AdminMenu.php:745` **Mechanism:** `'crm_pro_url' => 'https://fluentcrm.com/?utm_source=plugin&utm_medium=admin&utm_campaign=promo'` **Used by:** All PromoCard components for their "Upgrade to Pro" buttons **Already handled:** ✅ This is just a URL — since `has_campaign_pro` is true, users don't see it. --- ## GATE CATEGORY 8: MISSING HANDLERS (GAPS IN THE MU-PLUGIN) ### GAP 1: Pro triggers remain `disabled=true` (except PMPro) **File:** `ProFunnelItems.php` lines ~140-650+ **Issue:** ALL Pro triggers (WooCommerce, MemberPress, LearnDash, EDD, LifterLMS, etc.) have `disabled => true`. The mu-plugin only overrides PMPro triggers. Users cannot select WooCommerce/other Pro triggers for new funnels. **Fix needed:** Add to mu-plugin: ```php add_filter('fluentcrm_funnel_triggers', function($triggers) { foreach ($triggers as $key => $trigger) { if (isset($trigger['disabled'])) { $triggers[$key]['disabled'] = false; } } return $triggers; }, 1000); ``` ### GAP 2: Smart Links not enabled **Files:** `CampaignUrlMetric.php:306`, `AdminMenu.php:961-972` **Issue:** `fluent_crm/has_smartlink` filter returns false; `hasSmartLink()` checks for DB table. **Fix needed:** ```php add_filter('fluent_crm/has_smartlink', '__return_true'); ``` ### GAP 3: License/activation status — already handled **File:** mu-plugin lines 41-46 **Already handled:** ✅ Sets `_fluentcrm_license_status` to `valid` and `_fluentcrm_license_key` to `testing-license-key`. ### GAP 4: `fluent_crm/disable_fluentmail_suggest` filter **Already handled:** ✅ Not actively needed — defined in mu-plugin via `FLUENTMAIL` constant or via filter. ### GAP 5: Visual Builder template **Already handled:** ✅ With `FLUENTCAMPAIGN` defined, the `visual_builder_demo` fake template is NOT added to the list. --- ## COMPLETE LIST OF HANDLED vs. UNHANDLED GATES ### ✅ HANDLED by mu-plugin (v2.0): 1. All `defined('FLUENTCAMPAIGN')` checks (7+ locations) 2. All `defined('FLUENTCAMPAIGN_FRAMEWORK_VERSION')` checks (via `getActivatedFeatures()`) 3. All `defined('FLUENTCAMPAIGN_DIR_FILE')` checks (via deferred init priority 5) 4. PMPro disabled triggers (2 triggers un-disabled) 5. `fluentcrm_is_require_verify` filter 6. `fluentcrm_disable_email_open_tracking` filter 7. License status/key options 8. "Powered By FluentCRM" email footer branding 9. All JS `has_campaign_pro` computed property checks (because `window.fcAdmin.addons.fluentcampaign` is `true`) ### ❌ NOT HANDLED (gaps to fix): 1. **ALL non-PMPro Pro triggers remain `disabled=true`** — WooCommerce, MemberPress, LearnDash, LifterLMS, EDD, Restrict Content Pro, TutorLMS, Wishlist Member, SureCart, AffiliateWP, Abandoned Cart (~25+ triggers) 2. **Smart Links filter** — `fluent_crm/has_smartlink` returns false 3. **Smart Links DB table** — `fc_smart_links` table doesn't exist (would require Pro plugin activation or manual table creation) ### 🟡 PARTIALLY HANDLED: 1. PMPro triggers — the mu-plugin's filter at line 70-82 does handle these, but it's fragile (relies on trigger keys matching) and runs at priority 1000 which is late but workable. --- ## SUMMARY STATISTICS | Gate Category | Total | Handled | Not Handled | |---|---|---|---| | PHP constant checks (`FLUENTCAMPAIGN`) | ~20 | 20 | 0 | | PHP filter gates | ~4 | 2 | 2 | | JS/Vue `has_campaign_pro` checks | ~15 | 15 | 0 | | Disabled Pro triggers | ~25+ | 2 (PMPro) | ~23+ | | `is_pro` block flags | ~19 | 19 | 0 | | Email branding footers | ~6 | 6 | 0 | | CSS promo styling | ~3 | 3 | 0 | | **TOTAL** | **~92** | **~67** | **~25** | The core architecture of this mu-plugin is sound — the `FLUENTCAMPAIGN` constant unlocks all the major PHP backends and JS frontend gates. The two remaining gaps are: (1) adding a global `disabled` override for ALL Pro triggers (not just PMPro), and (2) enabling the Smart Links filter.